Triple
T2753930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tupolev Tu-20 / Tu-95 |
E61055
|
entity |
| Predicate | propellerConfiguration |
P17498
|
FINISHED |
| Object | contra-rotating propellers |
—
|
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: contra-rotating propellers | Statement: [Tupolev Tu-20 / Tu-95, propellerConfiguration, contra-rotating propellers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propellerConfiguration Context triple: [Tupolev Tu-20 / Tu-95, propellerConfiguration, contra-rotating propellers]
-
A.
propellerType
chosen
Indicates the specific kind or classification of propeller associated with an entity.
-
B.
propellerBlades
Indicates that something has propeller blades as a component or feature.
-
C.
numberOfPropellers
Indicates the quantity of propellers that an entity possesses or uses.
-
D.
rotorConfiguration
Indicates the specific arrangement and setup of rotors within a rotor-based system or mechanism.
-
E.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
- 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_69ab4b7a85bc819094a349b84beb1f2c |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb7073d081909da84b21015972f2 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd82d005c81908a1ac7a1313c6d88 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.