Triple
T13512716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valtion Lentokonetehdas |
E322677
|
entity |
| Predicate | designedAircraft |
P31176
|
FINISHED |
| Object | VL Viima |
E284556
|
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: VL Viima | Statement: [Valtion Lentokonetehdas, designedAircraft, VL Viima]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: VL Viima Context triple: [Valtion Lentokonetehdas, designedAircraft, VL Viima]
-
A.
VL Viima
chosen
The VL Viima is a Finnish two-seat biplane trainer aircraft used primarily for pilot training in the 1930s and 1940s.
-
B.
VL Pyry
VL Pyry was a Finnish World War II–era military trainer aircraft used primarily for pilot instruction by the Finnish Air Force.
-
C.
Viiala
Viiala was a former municipality in southern Finland that later became part of the town of Akaa.
-
D.
Vaino
Vaino is a given name, likely a variant or transliteration of the Finnish name Väinö, used as a personal first name.
-
E.
Vimpeli
Vimpeli is a small municipality in western Finland known for its rural character and strong Finnish baseball (pesäpallo) tradition.
- 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_69d80766a21881909f21a1b7421d3b8a |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf87ca288190a147fbdb2f90985f |
completed | April 12, 2026, 2:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75492676c81909602745e2b6436cb |
completed | May 3, 2026, 1:58 p.m. |
Created at: April 9, 2026, 9:44 p.m.