Triple
T13168288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udham Singh Nagar |
E312909
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Rudrapur |
E1026798
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Rudrapur | Statement: [Udham Singh Nagar, largestCity, Rudrapur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rudrapur Context triple: [Udham Singh Nagar, largestCity, Rudrapur]
-
A.
Rudrapur
Rudrapur is a town in the Indian state of Uttar Pradesh, known as a local commercial and agricultural center in the region.
-
B.
Rudrapur
chosen
Rudrapur is a rapidly developing industrial and commercial city in the Udham Singh Nagar district of Uttarakhand, India.
-
C.
Mukteshwar
Mukteshwar is a scenic hill town in Uttarakhand, India, known for its panoramic Himalayan views, fruit orchards, and tranquil forests.
-
D.
Nalhati
Nalhati is a town in the Birbhum district of West Bengal, India, known for its religious significance and regional marketplace.
-
E.
Ambarnath
Ambarnath is a suburban city in the Thane district of Maharashtra, India, known for its historic Shiva temple and its role as a residential and industrial hub near Mumbai.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c2c317881908cc715c97d915f77 |
completed | April 10, 2026, 11:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff0f24dc8190930eb8a987019024 |
completed | May 3, 2026, 7:53 a.m. |
Created at: April 9, 2026, 9:13 p.m.