Triple
T8921880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wardha Junction |
E212438
|
entity |
| Predicate | distanceToSevagram |
P86423
|
FINISHED |
| Object | approximately 6–10 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 6–10 km | Statement: [Wardha Junction, distanceToSevagram, approximately 6–10 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSevagram Context triple: [Wardha Junction, distanceToSevagram, approximately 6–10 km]
-
A.
distanceToSévaré
Indicates the spatial distance between a given entity and the location Sévaré.
-
B.
distanceFromGori
Indicates the spatial distance between a given entity or location and the place named Gori.
-
C.
distanceToSomnath
Indicates the spatial distance between a given entity or location and Somnath.
-
D.
distanceFromMina
Indicates the spatial distance measured between Mina and another specified entity or location.
-
E.
distanceToBingham
Indicates the measured or calculated distance between a given entity and the location named Bingham.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc665143688190872c681f4299bd9f |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
| PDg | Predicate description generation | batch_69cc600a59708190ae426044bbcd7929 |
completed | April 1, 2026, midnight |
Created at: March 30, 2026, 6:56 p.m.