Triple
T36209043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VL Tuisku |
E1047485
|
entity |
| Predicate | airForceService |
P94679
|
FINISHED |
| Object | Finnish Air Force |
—
|
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: Finnish Air Force | Statement: [VL Tuisku, airForceService, Finnish Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airForceService Context triple: [VL Tuisku, airForceService, Finnish Air Force]
-
A.
airForceUser
chosen
Indicates that an entity is a member of, affiliated with, or acting on behalf of an air force organization.
-
B.
airForceEquivalent
Indicates that one military unit, rank, or asset is the corresponding or analogous counterpart within an air force to another entity in a different branch or context.
-
C.
airForceRequirement
Indicates that an entity has a specified requirement or need related to an air force, such as capabilities, resources, or conditions that must be met.
-
D.
airForceCommand
Indicates a command relationship in which one entity exercises authority over the operations, organization, or administration of an air force or air force unit.
-
E.
usedByAirForce
Indicates that something is employed, operated, or otherwise utilized by an air force.
- F. None of above.
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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b57b8c5081909ba41145ba7753d1 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.