Triple
T31788969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Umeå |
E811408
|
entity |
| Predicate | isKeyPortIn |
P22777
|
FINISHED |
| Object | northern Sweden |
—
|
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: northern Sweden | Statement: [Port of Umeå, isKeyPortIn, northern Sweden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isKeyPortIn Context triple: [Port of Umeå, isKeyPortIn, northern Sweden]
-
A.
hasKeyPort
Indicates that an entity possesses or is associated with a primary or main port used for connection, access, or communication.
-
B.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
-
C.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another entity.
-
D.
isInKey
Indicates that something is located within, or belongs to, a specified key or key-based grouping in a structured context.
-
E.
keyPort
chosen
Indicates that a port serves as a primary or central connection point in a system or network.
- 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_69f348e60748819082dcaa7792659803 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 30, 2026, 11:38 p.m.