Triple
T8921476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinganghat |
E212425
|
entity |
| Predicate | distanceToNagpur_km |
P34372
|
FINISHED |
| Object | approximately 75 |
—
|
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 75 | Statement: [Hinganghat, distanceToNagpur_km, approximately 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToNagpur_km Context triple: [Hinganghat, distanceToNagpur_km, approximately 75]
-
A.
distanceToNagpur
chosen
Indicates the spatial distance between a given entity’s location and the city of Nagpur.
-
B.
distanceFromNashik
Indicates the spatial distance between a given entity or location and the city of Nashik.
-
C.
distanceToWardha
Indicates the spatial distance between a given entity and the location named Wardha.
-
D.
distanceToDelhiByRoad_km
Indicates the road travel distance, measured in kilometers, from a given place to Delhi.
-
E.
distanceToPandharpur
Indicates the measured or estimated spatial distance between a given location and the place Pandharpur.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc665024f081909515e02e5f5b2221 |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.