Triple
T19905000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yak-1 |
E478389
|
entity |
| Predicate | engineModel |
P2092
|
FINISHED |
| Object | Klimov M-105 |
—
|
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: Klimov M-105 | Statement: [Yak-1, engineModel, Klimov M-105]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klimov M-105 Context triple: [Yak-1, engineModel, Klimov M-105]
-
A.
Klimov M-100
The Klimov M-100 was a Soviet liquid-cooled V-12 aircraft engine developed in the 1930s as a domestically produced powerplant for fighters and bombers.
-
B.
Klimov VK-1
The Klimov VK-1 is a Soviet turbojet engine developed in the early Cold War era, widely used to power fighter aircraft such as the MiG-15 and MiG-17.
-
C.
Myasishchev M-4
The Myasishchev M-4 was a Soviet long-range strategic jet bomber developed in the 1950s as part of the Cold War nuclear deterrent force.
-
D.
Klimov VK‑105PF‑2
chosen
The Klimov VK‑105PF‑2 was a Soviet liquid-cooled V-12 piston aircraft engine widely used in World War II fighters.
-
E.
Lotarev D-36
The Lotarev D-36 is a Soviet-era high-bypass turbofan engine widely used on regional jets and military transport aircraft.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65945cc2081908224902d5f042d7a |
completed | April 20, 2026, 4:50 p.m. |
Created at: April 10, 2026, 1:52 p.m.