Triple
T22660268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klimov RD-45 |
E559641
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Klimov |
—
|
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 | Statement: [Klimov RD-45, manufacturer, Klimov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Klimov Context triple: [Klimov RD-45, manufacturer, Klimov]
-
A.
Klimov
chosen
Klimov is a Russian aerospace company renowned for designing and producing military and civilian gas-turbine engines, particularly for fighter aircraft and helicopters.
-
B.
Kuznetsov
Kuznetsov is a common Russian surname borne by numerous notable figures in fields such as politics, science, sports, and the arts.
-
C.
Shaposhnikov
Shaposhnikov is a Russian surname most notably associated with Soviet military leader Boris Shaposhnikov.
-
D.
Glushko
Glushko is a Russian surname most prominently associated with Valentin Glushko, a leading Soviet rocket engineer and pioneer of space propulsion.
-
E.
Mihaylovski
Mihaylovski is a Bulgarian surname, notably borne by the 19th-century cleric and national revival figure Ilarion Makariopolski.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765edf88819086c28525e3c73758 |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 3:07 p.m.