Triple
T31433164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spiral Tunnels |
E801849
|
entity |
| Predicate | locatedInPass |
P11383
|
FINISHED |
| Object | Kicking Horse Pass |
—
|
NE NERFINISHED |
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: Kicking Horse Pass | Statement: [Spiral Tunnels, locatedInPass, Kicking Horse Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPass Context triple: [Spiral Tunnels, locatedInPass, Kicking Horse Pass]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locationOfPassage
chosen
Indicates the place or area through which a passage, route, or transit occurs or is situated.
-
C.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
-
D.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
E.
locatedWith
Indicates that two or more entities are situated together in the same place or spatial context.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a018c6b7178819097d5450a1e3c2408 |
completed | May 11, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_6a018a4f741c8190babe721a908e2f5e |
completed | May 11, 2026, 7:50 a.m. |
Created at: April 30, 2026, 8:59 p.m.