Triple
T23326099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roads End trailhead |
E591296
|
entity |
| Predicate | positionInCanyon |
P72401
|
FINISHED |
| Object | upper end of Lamoille Canyon |
—
|
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: upper end of Lamoille Canyon | Statement: [Roads End trailhead, positionInCanyon, upper end of Lamoille Canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInCanyon Context triple: [Roads End trailhead, positionInCanyon, upper end of Lamoille Canyon]
-
A.
isInCanyon
chosen
Indicates that an entity is located within the geographical bounds of a canyon.
-
B.
elevationRelativeToCanyonFloor
Indicates the vertical height or altitude of something measured relative to the canyon floor as the reference level.
-
C.
elevationRelativeToCanyon
Indicates the relative height or altitude of one location compared to the canyon’s reference level.
-
D.
containsCanyon
Indicates that one geographic or spatial entity includes a canyon within its boundaries or extent.
-
E.
positionInCanal
Indicates that an entity occupies a specific location within a canal.
- 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_69e25d1effe4819096907f95f610dbff |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197e9de788190afd6883c7eac4854 |
completed | April 29, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69effcf8ca2c8190887d4f4656617d21 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:12 p.m.