Triple
T11617901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klimov VK-1 |
E275555
|
entity |
| Predicate | typicalAircraftInstallation |
P10706
|
FINISHED |
| Object | twin-engine bomber (Il-28) |
—
|
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: twin-engine bomber (Il-28) | Statement: [Klimov VK-1, typicalAircraftInstallation, twin-engine bomber (Il-28)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalAircraftInstallation Context triple: [Klimov VK-1, typicalAircraftInstallation, twin-engine bomber (Il-28)]
-
A.
avionicsSupplier
Indicates that one entity supplies avionics systems, components, or related services to another entity.
-
B.
aircraftEngineMounting
Indicates that an aircraft engine is attached or secured to a supporting structure or mounting point on the aircraft.
-
C.
isPartOfAviationSystem
Indicates that something functions as a component or subsystem within a broader aviation system or infrastructure.
-
D.
usedOnAircraftName
chosen
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
E.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a047758081908191c1d564409d9a |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.