Triple
T8160727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan Pass |
E190570
|
entity |
| Predicate | onDrainageDivideBetween |
P34484
|
FINISHED |
| Object | Pacific Ocean watershed |
—
|
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: Pacific Ocean watershed | Statement: [Logan Pass, onDrainageDivideBetween, Pacific Ocean watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onDrainageDivideBetween Context triple: [Logan Pass, onDrainageDivideBetween, Pacific Ocean watershed]
-
A.
drainageDivideOf
Indicates that one geographic feature functions as the drainage divide (separating water flow into different basins) for another feature or area.
-
B.
drainsInto
Indicates that one entity serves as a source or conduit whose contents or flow are directed into another entity.
-
C.
watershedBetween
chosen
Indicates that a geographic feature or boundary serves as the dividing line between two drainage basins or river systems.
-
D.
drainageInfluencedBy
Indicates that the pattern, direction, or effectiveness of drainage is affected or controlled by another factor or entity.
-
E.
dividedBetween
Indicates that something is partitioned or shared among two or more distinct entities or groups.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb455559188190bf95d9d93bb76002 |
completed | March 31, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69cb36a4c40c81909f60aef0e1624c13 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:38 p.m.