Triple
T37284930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jabalpur tourism circuit |
E925503
|
entity |
| Predicate | stateCapitalDistanceFromJabalpur |
P58719
|
FINISHED |
| Object | approximately 320 km from Bhopal |
—
|
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 320 km from Bhopal | Statement: [Jabalpur tourism circuit, stateCapitalDistanceFromJabalpur, approximately 320 km from Bhopal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateCapitalDistanceFromJabalpur Context triple: [Jabalpur tourism circuit, stateCapitalDistanceFromJabalpur, approximately 320 km from Bhopal]
-
A.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur to another place or entity.
-
B.
distanceFromJaipur
Indicates the spatial distance between a given entity and the location Jaipur.
-
C.
distanceToJodhpur
Indicates the spatial distance between a given entity or location and the city of Jodhpur.
-
D.
distanceFromBhopal
chosen
Indicates the measured spatial distance between a given location or entity and the city of Bhopal.
-
E.
stateCapitalDistance_Ranchi_km
Indicates the distance, measured in kilometers, between Ranchi and the capital city of its state.
- F. None of above.
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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 3, 2026, 4:16 p.m.