Triple
T26374338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luftstreitkräfte der Nationalen Volksarmee |
E660852
|
entity |
| Predicate | usedHelicopterType |
P75869
|
FINISHED |
| Object | Mi-8 |
—
|
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: Mi-8 | Statement: [Luftstreitkräfte der Nationalen Volksarmee, usedHelicopterType, Mi-8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedHelicopterType Context triple: [Luftstreitkräfte der Nationalen Volksarmee, usedHelicopterType, Mi-8]
-
A.
usedHelicopterModel
chosen
Indicates that a particular helicopter model was employed or utilized in relation to a given event, operation, or activity.
-
B.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
C.
isHelicopterVariantOf
Indicates that one helicopter model is a modified or derived version of another helicopter model.
-
D.
canOperateHelicopterType
Indicates that one entity has the ability, qualification, or authorization to operate or pilot a specified type of helicopter.
-
E.
isHelicopterOnly
Indicates that the subject is restricted to or designated exclusively for use by helicopters.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6106e60e48190829fa2ab14bcbbdf |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 11 p.m.