Triple
T24973552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skookumchuck Trail |
E624955
|
entity |
| Predicate | approachesSideOf |
P30202
|
FINISHED |
| Object | north side of Mount Lafayette |
—
|
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: north side of Mount Lafayette | Statement: [Skookumchuck Trail, approachesSideOf, north side of Mount Lafayette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approachesSideOf Context triple: [Skookumchuck Trail, approachesSideOf, north side of Mount Lafayette]
-
A.
hasApproachSide
chosen
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
B.
approachOver
Indicates that one entity moves closer to another entity from a position above or higher than it.
-
C.
approachDirection
Indicates the direction or bearing from which one entity moves closer to or advances toward another entity.
-
D.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
-
E.
onSide
Indicates that one entity is positioned along or adjacent to the side of another entity.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 18, 2026, 6:01 a.m.