Triple
T17600793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Länkipohja |
E428693
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Länkipohja |
—
|
NE NERFINISHED |
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: Länkipohja | Statement: [Battle of Länkipohja, location, Länkipohja]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Länkipohja Context triple: [Battle of Länkipohja, location, Länkipohja]
-
A.
Länkipohja
chosen
Länkipohja is a village in Finland historically noted as the site of the Battle of Länkipohja during the Finnish Civil War.
-
B.
Pöytyä
Pöytyä is a rural municipality in southwestern Finland known for its forests, agriculture, and small village communities.
-
C.
Oikotie
Oikotie is a Finnish online marketplace and classifieds platform, best known for its housing and job listings.
-
D.
Köyliö
Köyliö is a small former municipality in western Finland known for its rural landscape and historical significance, particularly in the Satakunta region.
-
E.
Laakso
Laakso is a residential district in Helsinki, Finland, known for its green areas and proximity to central neighborhoods like Meilahti.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c48dfc08190ba360e6082cffa87 |
completed | April 19, 2026, 5:46 a.m. |
Created at: April 10, 2026, 5:51 a.m.