Triple
T24797171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eider River |
E620416
|
entity |
| Predicate | Eider BarrageLocatedNear |
P28855
|
FINISHED |
| Object | Tönning |
—
|
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: Tönning | Statement: [Eider River, Eider BarrageLocatedNear, Tönning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Eider BarrageLocatedNear Context triple: [Eider River, Eider BarrageLocatedNear, Tönning]
-
A.
locatedInEstuarySystem
Indicates that something is situated within or forms part of an estuary system, where riverine and marine environments interact.
-
B.
locatedOnEasternShoreOf
Indicates that one entity is situated on the eastern shore or bank of another geographic feature, such as a body of water or landform.
-
C.
hasEstuaryNear
chosen
Indicates that the estuary of a water body is located in close proximity to a specified place or feature.
-
D.
hasEstuaryAt
Indicates that a river or watercourse flows into and meets a larger body of water (such as a sea, ocean, or lake) at a specific location.
-
E.
estuaryName
Indicates the naming relationship that assigns a specific name to an estuary.
- 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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f412a660648190a343347e6ff36ea5 |
completed | May 1, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:48 a.m.