Triple
T26864154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plateau Point Trail |
E676417
|
entity |
| Predicate | hasApproximateOneWayDistanceFromIndianGarden |
P174340
|
FINISHED |
| Object | 1.5 miles |
—
|
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: 1.5 miles | Statement: [Plateau Point Trail, hasApproximateOneWayDistanceFromIndianGarden, 1.5 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateOneWayDistanceFromIndianGarden Context triple: [Plateau Point Trail, hasApproximateOneWayDistanceFromIndianGarden, 1.5 miles]
-
A.
distanceFromGurugram_km
Indicates the physical distance, measured in kilometers, between an entity’s location and Gurugram.
-
B.
distanceFromDwarka
Indicates the spatial distance between a given entity and the location Dwarka.
-
C.
distanceFromGhaziabad
Indicates the measured or specified distance separating a given entity or location from Ghaziabad.
-
D.
distanceFromBengaluru
Indicates the measured spatial distance between a given entity’s location and the city of Bengaluru.
-
E.
distanceFromPune
Indicates the spatial distance between a given location or entity and the city of Pune.
- 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 27, 2026, 5:27 a.m.