Triple
T7635788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Finland |
E172874
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Lohja |
E212980
|
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: Lohja | Statement: [Southern Finland, contains, Lohja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lohja Context triple: [Southern Finland, contains, Lohja]
-
A.
Lohja
chosen
Lohja is a town and municipality in southern Finland known for its lakes, limestone industry, and location within the Uusimaa region.
-
B.
Loviisa
Loviisa is a small coastal town and municipality in southern Finland known for its historic wooden houses, seaside location, and nuclear power plant.
-
C.
Ruokolahti
Ruokolahti is a rural municipality in South Karelia, southeastern Finland, known for its lake-rich landscapes and proximity to the Russian border.
-
D.
Kuokkala
Kuokkala is a residential district of the city of Jyväskylä in central Finland, known for its lakeside location and distinctive bridge connection to the city center.
-
E.
Loimaa
Loimaa is a town and municipality in southwestern Finland known for its agricultural surroundings and small-town character.
- 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa95e488190962c23609e0890a5 |
completed | March 27, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c89ac251308190a09814cc469d80fd |
completed | March 29, 2026, 3:21 a.m. |
Created at: March 27, 2026, 3:57 p.m.