Triple
T8942763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rauma |
E212942
|
entity |
| Predicate | hasPort |
P35
|
FINISHED |
| Object | Port of Rauma |
E597812
|
NE 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: Port of Rauma | Statement: [Rauma, hasPort, Port of Rauma]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Port of Rauma Context triple: [Rauma, hasPort, Port of Rauma]
-
A.
Port of Rauma
chosen
The Port of Rauma is a key Finnish seaport on the country’s west coast, serving as an important hub for international cargo traffic and maritime trade.
-
B.
Port of Kemi
The Port of Kemi is a Finnish seaport on the northern Gulf of Bothnia that serves as an important hub for regional industry and cargo traffic in Lapland.
-
C.
Port of Pori
The Port of Pori is a significant Finnish seaport on the west coast that serves as an important hub for the country’s maritime trade and cargo traffic.
-
D.
Port of Oulu
The Port of Oulu is a key Finnish seaport on the Gulf of Bothnia that serves as an important hub for regional cargo traffic and industry.
-
E.
Port of Mariehamn
The Port of Mariehamn is the main maritime gateway of Åland’s capital, serving as a key passenger and cargo hub in the Baltic Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66d93978819084b1a5c7c5dd2372 |
completed | April 1, 2026, 12:29 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc1f418708190b1272209f61e3a51 |
completed | April 3, 2026, 1:34 p.m. |
Created at: March 30, 2026, 6:58 p.m.