Triple
T26687536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gavleån |
E672786
|
entity |
| Predicate | mouthLocatedInBodyOfWater |
P43761
|
FINISHED |
| Object | Gulf of Bothnia |
—
|
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: Gulf of Bothnia | Statement: [Gavleån, mouthLocatedInBodyOfWater, Gulf of Bothnia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mouthLocatedInBodyOfWater Context triple: [Gavleån, mouthLocatedInBodyOfWater, Gulf of Bothnia]
-
A.
hasMouthOnCoastOf
Indicates that one entity’s mouth or outlet is located on the coast of another entity.
-
B.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
C.
hasIslandAtMouth
Indicates that a geographic feature, typically a river, has an island located at or near its mouth where it meets a larger body of water.
-
D.
hasMouthWaterbody
chosen
Indicates that a waterbody has a mouth, i.e., the location or feature where it empties or flows into another waterbody or area.
-
E.
mouthLocatedInAdministrativeEntity
Indicates that the place where a river ends (its mouth) is situated within a specific administrative region or jurisdiction.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f6173f709881909da3e62baa6c9781 |
completed | May 2, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 3:24 a.m.