Triple
T1837589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arvo Ylppö |
E41099
|
entity |
| Predicate | residence |
P75
|
FINISHED |
| Object | Helsinki |
E14163
|
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: Helsinki | Statement: [Arvo Ylppö, residence, Helsinki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Helsinki Context triple: [Arvo Ylppö, residence, Helsinki]
-
A.
Helsinki
chosen
Helsinki is the capital and largest city of Finland, known for its coastal location on the Baltic Sea, modern design, and vibrant cultural life.
-
B.
Turku
Turku is one of Finland’s oldest and historically most important cities, located on the southwest coast and known for its medieval heritage and major Baltic Sea port.
-
C.
Tampere
Tampere is a major industrial and cultural city in southern Finland, historically significant as a key battleground in the Finnish Civil War.
-
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.
Tallinn
Tallinn is the capital and largest city of Estonia, a historic Baltic Sea port known for its well-preserved medieval Old Town and strategic maritime location.
- 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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0380a4c81909a2ad0bfd97c884a |
completed | March 7, 2026, 4:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae8929b30c8190b21f16bcb6225406 |
completed | March 9, 2026, 8:47 a.m. |
Created at: March 4, 2026, 7:33 p.m.