Triple
T20130399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asirgarh Fort |
E490872
|
entity |
| Predicate | distanceFromBurhanpur |
P138787
|
FINISHED |
| Object | approximately 20 kilometers north |
—
|
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 20 kilometers north | Statement: [Asirgarh Fort, distanceFromBurhanpur, approximately 20 kilometers north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromBurhanpur Context triple: [Asirgarh Fort, distanceFromBurhanpur, approximately 20 kilometers north]
-
A.
distanceFromBharatpur
Indicates the spatial distance measured from the reference location Bharatpur to another place or entity.
-
B.
distanceFromPatna
Indicates the spatial distance between a given location and the city of Patna.
-
C.
distanceFromBhopal
Indicates the measured spatial distance between a given location or entity and the city of Bhopal.
-
D.
distanceToJamshedpur_km
Indicates the physical distance, measured in kilometers, between a given location and Jamshedpur.
-
E.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676183dc8190b65d0def681aaa1e |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:31 p.m.