Triple
T19395373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Etah |
E485174
|
entity |
| Predicate | distanceTo |
P350
|
FINISHED |
| Object | Mainpuri |
—
|
NE NERFINISHED |
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: Mainpuri | Statement: [Etah, distanceTo, Mainpuri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mainpuri Context triple: [Etah, distanceTo, Mainpuri]
-
A.
Mainpuri
chosen
Mainpuri is a city in the Indian state of Uttar Pradesh, known for its cultural heritage within the Braj region and its historical and agricultural significance.
-
B.
Medinipur
Medinipur is a parliamentary constituency and region in the Indian state of West Bengal, known for its historical significance and political importance.
-
C.
Purulia
Purulia is a town in eastern India known as the administrative headquarters of Purulia district and for its distinctive Chhau dance and scenic, hilly landscape.
-
D.
Purnea
Purnea is a prominent city in the Indian state of Bihar, known as a commercial and educational hub for the surrounding northeastern region.
-
E.
Sagarpur
Sagarpur is a densely populated residential locality in southwest Delhi, India, known for its bustling markets and proximity to the Palam area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61b4875ac8190a9c184c075b5db16 |
completed | April 20, 2026, 12:25 p.m. |
Created at: April 10, 2026, 1:36 p.m.