Triple
T14025566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MiG-29K |
E337447
|
entity |
| Predicate | basedOn |
P98
|
FINISHED |
| Object | MiG-29 |
E29099
|
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: MiG-29 | Statement: [MiG-29K, basedOn, MiG-29]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MiG-29 Context triple: [MiG-29K, basedOn, MiG-29]
-
A.
MiG-29
chosen
The MiG-29 is a Soviet-designed twin-engine multirole fighter aircraft known for its high maneuverability and widespread use by various air forces around the world.
-
B.
Sukhoi Su-27
The Sukhoi Su-27 is a Soviet-era twin-engine air superiority fighter aircraft renowned for its agility, long-range capability, and role as the basis for numerous advanced Russian fighter variants.
-
C.
MiG-31
The MiG-31 is a long-range, high-speed Soviet/Russian interceptor aircraft designed to engage airborne targets at high altitudes and in all weather conditions.
-
D.
Sukhoi Su-29
The Sukhoi Su-29 is a Russian two-seat aerobatic training aircraft derived from the Su-26, widely used for advanced pilot instruction and competitive aerobatics.
-
E.
MiG-27
The MiG-27 is a Soviet-era, variable-sweep wing ground-attack aircraft derived from the MiG-23 and optimized for low-level strike missions.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa6ca7481908976ce748a1957b1 |
completed | April 14, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feadf7fee48190bf58a1b4a603217e |
completed | May 9, 2026, 3:46 a.m. |
Created at: April 9, 2026, 10:20 p.m.