Triple
T31499059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagda |
E803624
|
entity |
| Predicate | distanceToIndore |
P203704
|
FINISHED |
| Object | approximately 110 km |
—
|
LITERAL 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: approximately 110 km | Statement: [Nagda, distanceToIndore, approximately 110 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToIndore Context triple: [Nagda, distanceToIndore, approximately 110 km]
-
A.
distanceToAhmedabad
Indicates the spatial distance between a given location or entity and the city of Ahmedabad.
-
B.
distanceToVadodara
Indicates the spatial distance between a given entity’s location and the city of Vadodara.
-
C.
distanceToLucknow
Indicates the spatial distance between a given entity’s location and the city of Lucknow.
-
D.
distanceToJalgaon_km
Indicates the physical distance, measured in kilometers, between an entity and the location Jalgaon.
-
E.
distanceFromBhopal
Indicates the measured spatial distance between a given location or entity and the city of Bhopal.
- F. None of above. chosen
Provenance (4 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01cb89ff448190b60ee3d148ce76fc |
completed | May 11, 2026, 12:28 p.m. |
| PD | Predicate disambiguation | batch_6a01ca7604b48190bb8643c17c3a8c85 |
completed | May 11, 2026, 12:24 p.m. |
| PDg | Predicate description generation | batch_6a01cb8914048190a5e60e5639b1f88b |
completed | May 11, 2026, 12:28 p.m. |
Created at: April 30, 2026, 9:43 p.m.