Triple
T34917947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portneuf Gap |
E1007054
|
entity |
| Predicate | mountainRangeOnOtherSide |
P182104
|
FINISHED |
| Object | Bannock Range |
—
|
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: Bannock Range | Statement: [Portneuf Gap, mountainRangeOnOtherSide, Bannock Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountainRangeOnOtherSide Context triple: [Portneuf Gap, mountainRangeOnOtherSide, Bannock Range]
-
A.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
B.
mountainRangeOnOneSide
chosen
Indicates that a mountain range is located along or borders one side of a specified geographic feature or area.
-
C.
sideOfMountain
Indicates that one entity is located on or corresponds to a particular side or face of a mountain relative to another entity.
-
D.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain range.
-
E.
borderMountainOf
Indicates that a mountain lies along or forms part of the border of a specified region or 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.