Triple
T13815437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helsinki region |
E332002
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Pornainen |
E992298
|
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: Pornainen | Statement: [Helsinki region, contains, Pornainen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pornainen Context triple: [Helsinki region, contains, Pornainen]
-
A.
Pornainen
chosen
Pornainen is a small rural municipality in southern Finland, located within the Greater Helsinki region.
-
B.
Pöytyä
Pöytyä is a rural municipality in southwestern Finland known for its forests, agriculture, and small village communities.
-
C.
Laakso
Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
-
D.
Pälkäne
Pälkäne is a municipality in southern Finland known for its lakeside landscapes and rural character.
-
E.
Lapua
Lapua is a small town in western Finland known for its historical significance, including a former state cartridge factory and its role in the Lapua Movement.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7c0e6d5cc819087ccdbfc00f16542 |
completed | May 3, 2026, 9:40 p.m. |
Created at: April 9, 2026, 10:12 p.m.