Triple
T7254828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hailuoto |
E157691
|
entity |
| Predicate | connectedTo |
P37
|
FINISHED |
| Object | Oulu |
E128725
|
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: Oulu | Statement: [Hailuoto, connectedTo, Oulu]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oulu Context triple: [Hailuoto, connectedTo, Oulu]
-
A.
Oulu
chosen
Oulu is a major city in northern Finland known for its technology industry, university, and position near the Gulf of Bothnia.
-
B.
Kuopio
Kuopio is a city in eastern Finland known for its lakeside setting, vibrant cultural life, and status as a regional center for education and commerce.
-
C.
Kokkola
Kokkola is a coastal city in western Finland known for its maritime heritage and role as a military and naval hub.
-
D.
Lahti
Lahti is a city in southern Finland known for its winter sports facilities, particularly ski jumping and cross-country skiing, and for hosting numerous international sporting events.
-
E.
Pori
Pori is a coastal city in western Finland known for its industrial heritage, port, and annual Pori Jazz Festival.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6eaa0c76c81909fe43ed6938a13ea |
completed | March 27, 2026, 8:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8f2ffec108190ab60b0777d97dd89 |
completed | March 29, 2026, 9:38 a.m. |
Created at: March 27, 2026, 2:56 p.m.