Triple
T8233270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bölkow Bo‑105 |
E192343
|
entity |
| Predicate | rotorBladeMaterial |
P80990
|
FINISHED |
| Object | fiberglass reinforced plastic |
—
|
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: fiberglass reinforced plastic | Statement: [Bölkow Bo‑105, rotorBladeMaterial, fiberglass reinforced plastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rotorBladeMaterial Context triple: [Bölkow Bo‑105, rotorBladeMaterial, fiberglass reinforced plastic]
-
A.
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.
-
B.
tailRotorBlades
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.
-
C.
propellerBlades
Indicates that something has propeller blades as a component or feature.
-
D.
propellerType
Indicates the specific kind or classification of propeller associated with an entity.
-
E.
propellerBladesPerPropeller
Indicates the number of blades associated with each individual propeller.
- 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_69ca82db5b90819085d1ad7c2e27bfcc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782658fc8190885dc267355ff245 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.