Triple
T15654928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maysville, Kentucky |
E376412
|
entity |
| Predicate | riverMileMarker |
P111954
|
FINISHED |
| Object | approximately Ohio River mile 408 |
—
|
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 Ohio River mile 408 | Statement: [Maysville, Kentucky, riverMileMarker, approximately Ohio River mile 408]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverMileMarker Context triple: [Maysville, Kentucky, riverMileMarker, approximately Ohio River mile 408]
-
A.
riverMilepost
chosen
Indicates the specific distance or position along a river, measured in miles from a defined starting point.
-
B.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
C.
riverMileFromMouth
Indicates the distance, measured in river miles, from the river’s mouth upstream to a specific point along the river.
-
D.
riverLocation
Indicates that a river is located in, passes through, or is geographically associated with a specified place or region.
-
E.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef1f83c8190bbf65eed162cbd55 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:15 a.m.