Triple
T27458588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sultanganj |
E692668
|
entity |
| Predicate | distanceToBhagalpur_km |
P200093
|
FINISHED |
| Object | about 25 |
—
|
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: about 25 | Statement: [Sultanganj, distanceToBhagalpur_km, about 25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBhagalpur_km Context triple: [Sultanganj, distanceToBhagalpur_km, about 25]
-
A.
distanceFromBurhanpur
Indicates the measured distance between a given place or object and the location of Burhanpur.
-
B.
distanceFromPatna
Indicates the spatial distance between a given location and the city of Patna.
-
C.
distanceToJamshedpur_km
Indicates the physical distance, measured in kilometers, between a given location and Jamshedpur.
-
D.
distanceToJalgaon_km
Indicates the physical distance, measured in kilometers, between an entity and the location Jalgaon.
-
E.
distanceFromBharatpur
Indicates the spatial distance measured from the reference location Bharatpur to another place or entity.
- 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_69ef5207903881909427745cda05d27a |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
| PDg | Predicate description generation | batch_69ff7594c6c081909e812e4e04e63530 |
completed | May 9, 2026, 5:57 p.m. |
Created at: April 27, 2026, 12:49 p.m.