Triple
T31788970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Umeå |
E811408
|
entity |
| Predicate | hasPassengerTrafficTo |
P108512
|
FINISHED |
| Object | 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: Finland | Statement: [Port of Umeå, hasPassengerTrafficTo, Finland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerTrafficTo Context triple: [Port of Umeå, hasPassengerTrafficTo, Finland]
-
A.
hasPassengerTrafficFrom
Indicates that an entity receives or handles passenger traffic originating from another entity.
-
B.
hasPassengerTrafficRank
Indicates the relative position or ranking of an entity based on the volume of passenger traffic it handles compared to others.
-
C.
hasHeavyPassengerTraffic
Indicates that an entity experiences a high volume of passenger movement or usage over a given period.
-
D.
servesPassengerTrafficTo
chosen
Indicates that a transportation facility or service provides regular passenger traffic access or operations to a particular location or area.
-
E.
passengerTraffic
Indicates the flow or volume of passengers moving through or using a particular transport service, route, or facility.
- 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_69fecd0a732c819097bdd3eb69b6158c |
completed | May 9, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69fecc0318d481908b5b20598a76a9fe |
completed | May 9, 2026, 5:54 a.m. |
Created at: April 30, 2026, 11:38 p.m.