Triple
T27745748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonnots Mill, Missouri |
E701976
|
entity |
| Predicate | hasHistoricUseOfRiver |
P121141
|
FINISHED |
| Object | transportation |
—
|
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: transportation | Statement: [Bonnots Mill, Missouri, hasHistoricUseOfRiver, transportation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricUseOfRiver Context triple: [Bonnots Mill, Missouri, hasHistoricUseOfRiver, transportation]
-
A.
hasAncestralRiver
Indicates that an entity is associated with or originates from a river regarded as its ancestral or traditional source.
-
B.
historicallyAssociatedRiver
Indicates a relationship where an entity has a notable historical connection or association with a particular river, such as through events, development, or cultural significance.
-
C.
hasRiverPortHistory
Indicates that an entity has a historical association with functioning as a river port or hosting river port activities.
-
D.
hasRiverUse
chosen
Indicates that one entity makes use of a river associated with another entity, such as for transport, irrigation, recreation, or other purposes.
-
E.
laterUseOfWaterway
Indicates that a waterway is used or utilized at a time subsequent to a previously referenced event or period.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 27, 2026, 4:15 p.m.