Triple
T34213946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marmet Lock and Dam |
E877733
|
entity |
| Predicate | riverMileOnKanawha |
P111954
|
FINISHED |
| Object | approximately 67 |
—
|
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: approximately 67 | Statement: [Marmet Lock and Dam, riverMileOnKanawha, approximately 67]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileOnKanawha Context triple: [Marmet Lock and Dam, riverMileOnKanawha, approximately 67]
-
A.
riverMilepost
chosen
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
B.
riverMileRange
Indicates a relationship specifying that something occurs, applies, or is located between two given mile markers along a river.
-
C.
riverMileFromMouth
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
D.
riverKilometerContext
Indicates the position or context of something along a river, measured in river kilometers from a defined reference point.
-
E.
riverMileBelowHooverDam
Indicates the position of a location along the river measured in miles downstream from Hoover Dam.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: May 1, 2026, 1:55 a.m.