Triple
T25754624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yonne River basin |
E648559
|
entity |
| Predicate | flowsUltimatelyInto |
P159234
|
FINISHED |
| Object | English Channel |
—
|
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: English Channel | Statement: [Yonne River basin, flowsUltimatelyInto, English Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsUltimatelyInto Context triple: [Yonne River basin, flowsUltimatelyInto, English Channel]
-
A.
flowsFrom
Indicates that a substance, medium, or influence moves or originates from one entity or location and proceeds outward to another.
-
B.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
C.
flowsOn
Indicates that one entity (typically a fluid or current) moves continuously along the surface or path defined by another entity.
-
D.
flowsOver
Indicates that one substance or medium moves across the surface or boundary of another, covering or passing above it.
-
E.
flowsUnder
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
- F. None of above. chosen
Provenance (4 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd81788c819096c045e9ef3ffc08 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 4:38 a.m.