Triple
T26180099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-54 |
E654650
|
entity |
| Predicate | rotorcraftType |
P89012
|
FINISHED |
| Object | single main rotor helicopter |
—
|
LITERAL 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: single main rotor helicopter | Statement: [Mil Mi-54, rotorcraftType, single main rotor helicopter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorcraftType Context triple: [Mil Mi-54, rotorcraftType, single main rotor helicopter]
-
A.
isHelicopterVariantOf
Indicates that one helicopter model is a modified or derived version of another helicopter model.
-
B.
isHelicopterOf
Indicates that one entity is a helicopter that belongs to, is operated by, or is otherwise associated with another entity.
-
C.
rotorType
chosen
Indicates the specific kind or category of rotor associated with an entity.
-
D.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
-
E.
typeOfAviation
Indicates the specific category or kind of aviation to which an entity belongs (e.g., commercial, military, private).
- 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_69ee5b45873c81909499203612d05d07 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c6f7d4c819087acf8c6de2cc895 |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:39 p.m.