Triple
T25478944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yser basin |
E638511
|
entity |
| Predicate | mouthOfMainRiver |
P3817
|
FINISHED |
| Object | North Sea |
—
|
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: North Sea | Statement: [Yser basin, mouthOfMainRiver, North Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthOfMainRiver Context triple: [Yser basin, mouthOfMainRiver, North Sea]
-
A.
mouthOfTheWatercourse
Indicates the location where a watercourse ends and flows into a larger body of water.
-
B.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
C.
mouthOfWatercourse
chosen
Indicates the location where a watercourse ends and flows into a larger body of water or another watercourse.
-
D.
majorPortAtMouth
Indicates that a major port is located at the mouth of a river where it meets a larger body of water.
-
E.
flowsIntoViaMainRiver
Indicates that one water body ultimately flows into another through the course of a primary or main river channel.
- 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_69e75db9b964819096802dcf502e577e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7737a1c81909933c73eacdfd6a8 |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:27 p.m.