Triple
T2894822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trail Crest |
E63910
|
entity |
| Predicate | trailMilepostOn |
P43845
|
FINISHED |
| Object | Mount Whitney Trail high point before summit |
—
|
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: Mount Whitney Trail high point before summit | Statement: [Trail Crest, trailMilepostOn, Mount Whitney Trail high point before summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailMilepostOn Context triple: [Trail Crest, trailMilepostOn, Mount Whitney Trail high point before summit]
-
A.
trailName
Indicates the name assigned to a specific trail or path in the relationship.
-
B.
crossesAtMilepost
Indicates that one entity crosses or intersects another at a specific milepost location.
-
C.
trailblazerFor
Indicates that one entity serves as a pioneering example, opening the way or setting a precedent for another entity to follow or build upon.
-
D.
trailNumber
Indicates that an entity is associated with a specific trail identifier or route number within a trail system.
-
E.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
- 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_69ab4c45822c8190830c5f2bb97bcfd0 |
completed | March 6, 2026, 9:51 p.m. |
| NER | Named-entity recognition | batch_69abe06509808190b673222b9ae3d599 |
completed | March 7, 2026, 8:23 a.m. |
| PD | Predicate disambiguation | batch_69abdd17bcdc8190aa47274a50ba4ad4 |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde0f4c648190b9812e64f30c39da |
completed | March 7, 2026, 8:13 a.m. |
Created at: March 6, 2026, 10:07 p.m.