Triple
T15714728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Region of Uusimaa |
E380931
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Vihti |
E231585
|
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: Vihti | Statement: [Region of Uusimaa, contains, Vihti]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vihti Context triple: [Region of Uusimaa, contains, Vihti]
-
A.
Vihti
chosen
Vihti is a municipality in southern Finland located within the Uusimaa region, known for its lakes, rural landscapes, and proximity to the Helsinki metropolitan area.
-
B.
Laakso
Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
-
C.
Kauhava
Kauhava is a town in western Finland known historically for its aviation activities and air base, as well as its traditional knife-making heritage.
-
D.
Raisio
Raisio is a town and municipality in southwestern Finland known for its industrial base and as the headquarters of the food company Raisio Group.
-
E.
Hyrylä
Hyrylä is the main built-up area and administrative center of the municipality of Tuusula in southern Finland.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f90aea0819082a9e9fe0f7780b0 |
completed | April 16, 2026, 2:55 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff82f22fc88190820ecb171041136d |
completed | May 9, 2026, 6:54 p.m. |
Created at: April 10, 2026, 4:45 a.m.