Triple
T9245468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Trent XWB |
E222180
|
entity |
| Predicate | fanBladeMaterial |
P80990
|
FINISHED |
| Object | titanium alloy |
—
|
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: titanium alloy | Statement: [Rolls-Royce Trent XWB, fanBladeMaterial, titanium alloy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBladeMaterial Context triple: [Rolls-Royce Trent XWB, fanBladeMaterial, titanium alloy]
-
A.
rotorBladeMaterial
chosen
Indicates the material from which a rotor blade is made or constructed.
-
B.
propellerBlades
Indicates that something has propeller blades as a component or feature.
-
C.
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.
-
D.
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.
-
E.
fanType
Indicates the specific category or kind of fan associated with an entity, such as its design, purpose, or operating principle.
- 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_69ca841d2b18819089f9faf5b2c2aec0 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd03efaa748190973916bd790f6e3a |
completed | April 1, 2026, 11:39 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.