Triple
T11046094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris Burn Hut |
E261138
|
entity |
| Predicate | trailDistanceContext |
P97473
|
FINISHED |
| Object | one of the main huts spaced along the Kepler Track |
—
|
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: one of the main huts spaced along the Kepler Track | Statement: [Iris Burn Hut, trailDistanceContext, one of the main huts spaced along the Kepler Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceContext Context triple: [Iris Burn Hut, trailDistanceContext, one of the main huts spaced along the Kepler Track]
-
A.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
B.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
C.
tourLength
Indicates the total duration or distance covered by a tour or route.
-
D.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
-
E.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7982f7e688190b3f0c249cd9b1a3e |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750c99f9881908ee2b01b6ce4b3a1 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:26 p.m.