Triple
T23687780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeffboat Inc. |
E585214
|
entity |
| Predicate | operatedOnWaterway |
P84216
|
FINISHED |
| Object | Ohio River |
—
|
NE NERFINISHED |
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: Ohio River | Statement: [Jeffboat Inc., operatedOnWaterway, Ohio River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedOnWaterway Context triple: [Jeffboat Inc., operatedOnWaterway, Ohio River]
-
A.
operatedOnWaterBody
chosen
Indicates that an entity performs its operation or activity on or in a specific body of water.
-
B.
operatedCanal
Indicates that one entity managed and ran the functioning of a canal for another entity or in a given context.
-
C.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
D.
isInlandWaterwayInfrastructure
Indicates that something is part of the physical facilities or structures used for inland waterway transport, such as canals, locks, or related navigational infrastructure.
-
E.
waterwayMaintainedBy
Indicates that a particular waterway is maintained, managed, or serviced by a specified agent or organization.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5bfe15c8190af2b4c451bccae16 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:52 p.m.