Triple
T25165477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Luleå |
E630160
|
entity |
| Predicate | partOfSeaArea |
P166112
|
FINISHED |
| Object | Bothnian Bay |
—
|
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: Bothnian Bay | Statement: [Port of Luleå, partOfSeaArea, Bothnian Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSeaArea Context triple: [Port of Luleå, partOfSeaArea, Bothnian Bay]
-
A.
hasSeaAreaName
Indicates that a sea area is associated with and identified by a specific name.
-
B.
appliesToSeaArea
Indicates that something (such as a rule, restriction, or designation) is relevant or valid within a specified sea area.
-
C.
seaAreaCode
Indicates the specific coded maritime or sea area associated with or relevant to an entity.
-
D.
isPartOfMaritimeZone
chosen
Indicates that one area or feature is contained within, or legally belongs to, a specified maritime zone.
-
E.
seaAreaA1Definition
Indicates the defined spatial extent or boundary description of a specific sea area labeled A1.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 21, 2026, 12:16 p.m.