Triple
T34917944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Portneuf Gap |
E1007054
|
entity |
| Predicate | traversesRange |
P111083
|
FINISHED |
| Object | Portneuf 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: Portneuf Range | Statement: [Portneuf Gap, traversesRange, Portneuf Range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traversesRange Context triple: [Portneuf Gap, traversesRange, Portneuf Range]
-
A.
alsoTraverses
Indicates that a route, path, or entity passes through or crosses an additional location or segment beyond its primary traversal.
-
B.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
-
C.
regionTraversedBy
chosen
Indicates that a region is crossed or passed through by a specified path, route, or linear feature.
-
D.
launcherTraverse
Indicates the movement or rotation of a launcher mechanism as it traverses across its operational arc or axis.
-
E.
testRange
Indicates that a value, condition, or behavior is being evaluated to determine whether it falls within a specified range or interval.
- 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_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.