Triple
T17156178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahod district |
E416348
|
entity |
| Predicate | largestCity |
P235
|
FINISHED |
| Object | Dahod |
E92666
|
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: Dahod | Statement: [Dahod district, largestCity, Dahod]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dahod Context triple: [Dahod district, largestCity, Dahod]
-
A.
Dahod
chosen
Dahod is a town in the Indian state of Gujarat, historically notable as the birthplace of the Mughal emperor Aurangzeb.
-
B.
Navsari
Navsari is a city in the Indian state of Gujarat known historically as a center of Parsi culture and commerce.
-
C.
Jhabua
Jhabua is a town and administrative district headquarters in western Madhya Pradesh, India, known for its significant tribal population and culture.
-
D.
Dhrol
Dhrol is a town in the Jamnagar district of Gujarat, India, known historically as the seat of the former princely Dhrol State.
-
E.
Khargone
Khargone is a city in western Madhya Pradesh, India, known as an agricultural and commercial center in the Nimar 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f40b402881908b8c01d7b957d0d2 |
completed | April 18, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a015fc46c308190b09efb13776747e7 |
completed | May 11, 2026, 4:49 a.m. |
Created at: April 10, 2026, 5:37 a.m.