Triple
T1026823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CH-148 Cyclone |
E22156
|
entity |
| Predicate | tailRotorConfiguration |
P24155
|
FINISHED |
| Object | conventional tail rotor |
—
|
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: conventional tail rotor | Statement: [CH-148 Cyclone, tailRotorConfiguration, conventional tail rotor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailRotorConfiguration Context triple: [CH-148 Cyclone, tailRotorConfiguration, conventional tail rotor]
-
A.
propellerType
Indicates the specific kind or classification of propeller associated with an entity.
-
B.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
C.
landingGearType
Indicates the specific kind or configuration of landing gear that an object (typically an aircraft or vehicle) uses.
-
D.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
E.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
- F. None of above. chosen
Provenance (4 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_69a493d6e380819097b384986ffc315c |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b95d35888190a20593a278175df7 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7276180819085c6b23501a6a6e0 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b95bb5908190ad1d5f5e0d8f664d |
completed | March 1, 2026, 10:10 p.m. |
Created at: March 1, 2026, 7:41 p.m.