Triple
T2093840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gulf of Finland |
E32733
|
entity |
| Predicate | westernConnection |
P16483
|
FINISHED |
| Object | Baltic Sea main basin |
—
|
LITERAL FINISHED |
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: Baltic Sea main basin | Statement: [Gulf of Finland, westernConnection, Baltic Sea main basin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernConnection Context triple: [Gulf of Finland, westernConnection, Baltic Sea main basin]
-
A.
westernGate
chosen
Indicates that one entity serves as the western gate or western entrance relative to another entity.
-
B.
northernConnection
Indicates a relationship where one entity is connected to another primarily through or via its northern side, direction, or region.
-
C.
southernConnection
Indicates a relationship where one entity is connected to, associated with, or accessed via the southern part or side of another entity.
-
D.
westernSpanType
Indicates the type or classification of the span located on the western side of a structure or system.
-
E.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
- 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_69a885eba0708190999696a45cbec816 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abba98c32081908a243bc7088a1510 |
completed | March 7, 2026, 5:41 a.m. |
| PD | Predicate disambiguation | batch_69abb7b6274081909df36cd7a7c6a675 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.