Triple
T14590146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadaat-e-Zaidpur |
E342422
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Zaidpur |
E1044923
|
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: Zaidpur | Statement: [Sadaat-e-Zaidpur, locatedIn, Zaidpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zaidpur Context triple: [Sadaat-e-Zaidpur, locatedIn, Zaidpur]
-
A.
Zaidpur
chosen
Zaidpur is a town in the Barabanki district of Uttar Pradesh, India, known for its local markets and traditional crafts.
-
B.
Mubarakpur
Mubarakpur is a town in Uttar Pradesh, India, known for its traditional handloom weaving and production of fine silk sarees.
-
C.
Daryapur
Daryapur is a town in the Amravati district of Maharashtra, India, known for its agricultural economy and regional market activities.
-
D.
Bazpur
Bazpur is a town in the Udham Singh Nagar district of Uttarakhand, India, known for its agricultural economy and proximity to the foothills of the Himalayas.
-
E.
Gadarpur
Gadarpur is a town in the Udham Singh Nagar district of Uttarakhand, India, known primarily as an agricultural and trading center in the Terai region.
- 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_69d822ddc0f081909cd8163c7de298cd |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4249af08190962009741d1f7d41 |
completed | April 14, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdd5c79c488190a134d2b0435e899e |
completed | May 8, 2026, 12:23 p.m. |
Created at: April 10, 2026, 1:24 a.m.