Triple
T31898694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallinn Bay |
E814358
|
entity |
| Predicate | bodyOfWaterOf |
P1778
|
FINISHED |
| Object | Gulf of Finland |
—
|
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 Finland | Statement: [Tallinn Bay, bodyOfWaterOf, Gulf of Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyOfWaterOf Context triple: [Tallinn Bay, bodyOfWaterOf, Gulf of Finland]
-
A.
bodyOfWater
chosen
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
B.
formsBodyOfWater
Indicates that one entity constitutes or creates the physical substance or structure that makes up a particular body of water.
-
C.
connectedBodyOfWater
Indicates that two geographic locations are linked by a continuous body of water through which water can flow between them.
-
D.
landingBodyOfWater
Indicates that an entity (such as an aircraft or vessel) lands on or comes to rest upon a specified body of water.
-
E.
addressesWaterBody
Indicates that an action, plan, or measure is directed toward managing, affecting, or dealing with a specific water body.
- 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_69f348f04d7881909537fc9e7cbc670e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b166b4788190997dc7d7b865a428 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:59 p.m.