Triple
T16165366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hisar Airport |
E392288
|
entity |
| Predicate | distanceToDelhiApprox |
P42970
|
FINISHED |
| Object | about 160 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: about 160 km | Statement: [Hisar Airport, distanceToDelhiApprox, about 160 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToDelhiApprox Context triple: [Hisar Airport, distanceToDelhiApprox, about 160 km]
-
A.
distanceToDelhiApproxKm
chosen
Indicates the approximate distance, measured in kilometers, between a given entity’s location and Delhi.
-
B.
distanceToDelhiByRoad_km
Indicates the road travel distance, measured in kilometers, from a given place to Delhi.
-
C.
distanceToDelhiByRail_km
Indicates the distance, measured in kilometers, from a given place to Delhi when traveling by rail.
-
D.
distanceToChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity and the city of Chandigarh.
-
E.
distanceFromChandigarh_km
Indicates the physical distance, measured in kilometers, between an entity’s location and the city of Chandigarh.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb2a25c819095437b25e6ab83f3 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.