Triple
T26934656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canoe Capital of Ohio |
E678337
|
entity |
| Predicate | relatedToRiver |
P180780
|
FINISHED |
| Object | Mohican 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: Mohican River | Statement: [Canoe Capital of Ohio, relatedToRiver, Mohican River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedToRiver Context triple: [Canoe Capital of Ohio, relatedToRiver, Mohican River]
-
A.
linkedToRiver
chosen
Indicates a relationship where something is physically or functionally connected to, associated with, or dependent on a river.
-
B.
closelyAssociatedRiver
Indicates a river that is geographically or functionally closely connected to the subject, such as flowing nearby, through, or otherwise strongly linked to it.
-
C.
associatedRiverBasin
Indicates that one entity is linked to, or lies within the drainage area of, a particular river basin.
-
D.
riverRelation
Indicates a spatial or geographic relationship between one river and another, such as confluence, branching, or relative positioning.
-
E.
mainRiverAssociated
Indicates that one entity is associated with, or primarily linked to, a particular main river.
- 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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69ff0491409c8190be40f633a58da0b1 |
completed | May 9, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69ff040bb5cc81909534c7eee85d5e90 |
completed | May 9, 2026, 9:53 a.m. |
Created at: April 27, 2026, 6:14 a.m.