Triple
T7100168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mil Mi-8 |
E165435
|
entity |
| Predicate | variant |
P4680
|
FINISHED |
| Object | Mi-8MT |
E31127
|
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: Mi-8MT | Statement: [Mil Mi-8, variant, Mi-8MT]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mi-8MT Context triple: [Mil Mi-8, variant, Mi-8MT]
-
A.
Mi-8
chosen
The Mi-8 is a Soviet-designed twin-turbine transport helicopter widely used around the world for both military and civilian roles.
-
B.
Mi-17
The Mi-17 is a Russian-designed, medium-lift military transport helicopter widely used for troop transport, cargo missions, and search-and-rescue operations.
-
C.
Mil Mi-14
The Mil Mi-14 is a Soviet amphibious anti-submarine and search-and-rescue helicopter developed from the Mi-8 and used primarily by naval aviation forces.
-
D.
Mil Mi-2
The Mil Mi-2 is a Soviet light utility helicopter widely used for transport, training, and various civilian and military roles since the 1960s.
-
E.
Mil Mi-60
The Mil Mi-60 is a proposed light utility helicopter concept developed by Russia’s Mil design bureau as a modern, compact rotorcraft for civilian and military applications.
- 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_69c6887fcddc8190a5d58908f6dee590 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e58531c88190a32746f9a97da709 |
completed | March 27, 2026, 8:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8682696a48190aec021bd00c6f633 |
completed | March 28, 2026, 11:45 p.m. |
Created at: March 27, 2026, 2:42 p.m.