Triple
T21740061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellsburg, West Virginia |
E536630
|
entity |
| Predicate | hasRiverPortActivity |
P1477
|
FINISHED |
| Object | barges on the Ohio River |
—
|
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: barges on the Ohio River | Statement: [Wellsburg, West Virginia, hasRiverPortActivity, barges on the Ohio River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverPortActivity Context triple: [Wellsburg, West Virginia, hasRiverPortActivity, barges on the Ohio River]
-
A.
hasRiverPortPotential
Indicates that a location has suitable conditions to support the development or operation of a river port.
-
B.
hasRiverActivity
chosen
Indicates that an entity engages in, supports, or is associated with activities occurring on or along a river.
-
C.
hasNotableRiverPort
Indicates that a place possesses a river port recognized for its significance in transport, trade, or regional importance.
-
D.
connectsToRiverPort
Indicates that one location, route, or infrastructure element has a direct linkage or access to a river port.
-
E.
hasRiverPortStatus
Indicates that an entity holds the status of having a river port, meaning it is officially recognized as a location where river-based shipping or transport operations occur.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a714c208190b96efe23ed3bf0db |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.