Triple
T22018139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lappo |
E543765
|
entity |
| Predicate | location |
P40
|
FINISHED |
| Object | Lapua |
—
|
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: Lapua | Statement: [Battle of Lappo, location, Lapua]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lapua Context triple: [Battle of Lappo, location, Lapua]
-
A.
Lapua
chosen
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.
-
B.
Kilkea
Kilkea is a small village in County Kildare, Ireland, best known for its historic medieval castle and surrounding rural landscape.
-
C.
Kangasala
Kangasala is a Finnish town and municipality in the Pirkanmaa region, known for its scenic ridge landscapes and lakes.
-
D.
Savonranta
Savonranta is a small locality in Eastern Finland known for its proximity to the lake-dotted wilderness and islands of the Saimaa region.
-
E.
Pukkila
Pukkila is a small rural municipality in southern Finland, located within the Greater Helsinki region.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127c4e0088190a5241d1b87d746da |
completed | April 28, 2026, 9:33 p.m. |
Created at: April 16, 2026, 8:23 p.m.