Triple
T37493884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skipanon River estuary |
E931772
|
entity |
| Predicate | isAtConfluenceOf |
P11842
|
FINISHED |
| Object | Skipanon 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: Skipanon River | Statement: [Skipanon River estuary, isAtConfluenceOf, Skipanon River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAtConfluenceOf Context triple: [Skipanon River estuary, isAtConfluenceOf, Skipanon River]
-
A.
isBelievedToBeConfluenceOf
Indicates that something is regarded or considered to be the point where multiple elements, sources, or influences come together.
-
B.
locatedAtConfluenceOf
chosen
Indicates that something is situated at the meeting point where two or more bodies of water or similar flowing features join together.
-
C.
hasRiverConfluenceFunction
Indicates that something serves as a location or feature where two or more rivers meet and merge their flows.
-
D.
hasConfluencePointAt
Indicates that two or more flows, paths, or entities meet and merge at a specific point.
-
E.
startsAfterConfluenceOf
Indicates that one entity begins at a point located downstream from, and subsequent to, the confluence where two or more other entities merge.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.