Triple
T8951963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Granite Dam |
E213372
|
entity |
| Predicate | riverMileOnSnakeRiver |
P55788
|
FINISHED |
| Object | 107 |
—
|
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: 107 | Statement: [Lower Granite Dam, riverMileOnSnakeRiver, 107]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileOnSnakeRiver Context triple: [Lower Granite Dam, riverMileOnSnakeRiver, 107]
-
A.
riverMileFromMouth
chosen
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
B.
riverMileBelowHooverDam
Indicates the position of a location along the river measured in miles downstream from Hoover Dam.
-
C.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
D.
distanceToWinnemucca
Indicates the spatial distance between a given entity’s location and the location of Winnemucca.
-
E.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670dc0c88190b1f59e96ad88e4ee |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed74d288190b712d739805579dc |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.