Triple
T1722049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airbus H145 |
E37412
|
entity |
| Predicate | rotorBladesTail |
P27709
|
FINISHED |
| Object | Fenestron multi‑blade |
—
|
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: Fenestron multi‑blade | Statement: [Airbus H145, rotorBladesTail, Fenestron multi‑blade]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorBladesTail Context triple: [Airbus H145, rotorBladesTail, Fenestron multi‑blade]
-
A.
tailRotorBlades
chosen
Indicates the relationship in which an entity functions as the rotor blades located at the tail of a rotorcraft, used for stability and directional control.
-
B.
mainRotorBlades
Indicates the relationship between a helicopter’s main rotor assembly and the blades that are attached to and rotate as part of that primary lifting rotor system.
-
C.
tailRotorConfiguration
Indicates the specific arrangement or design setup of a vehicle’s tail rotor relative to its main structure or propulsion system.
-
D.
propellerType
Indicates the specific kind or classification of propeller associated with an entity.
-
E.
rotorConfiguration
Indicates the specific arrangement and setup of rotors within a rotor-based system or mechanism.
- 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_69a8861acab88190bb43cde203429399 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aadb7bda1081908f2c41c520c9c55c |
completed | March 6, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69aa61c0a0288190bce9d60062a84b69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.