Triple
T23825095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tirathgarh Falls |
E589345
|
entity |
| Predicate | distanceFromJagdalpurApprox |
P153768
|
FINISHED |
| Object | 35 kilometres |
—
|
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: 35 kilometres | Statement: [Tirathgarh Falls, distanceFromJagdalpurApprox, 35 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromJagdalpurApprox Context triple: [Tirathgarh Falls, distanceFromJagdalpurApprox, 35 kilometres]
-
A.
distanceFromJabalpur
Indicates the spatial distance measured from the reference location Jabalpur to another place or entity.
-
B.
distanceToJodhpur
Indicates the spatial distance between a given entity or location and the city of Jodhpur.
-
C.
distanceToJamshedpur_km
Indicates the physical distance, measured in kilometers, between a given location and Jamshedpur.
-
D.
distanceFromJaipur
Indicates the spatial distance between a given entity and the location Jaipur.
-
E.
distanceFromBurhanpur
Indicates the measured distance between a given place or object and the location of Burhanpur.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f04bdc8190842a287a86b60d3a |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
| PDg | Predicate description generation | batch_69f158b0e320819090b947ee7eb14116 |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 17, 2026, 8 p.m.