Triple
T25757035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce BR725 A1-12 |
E648627
|
entity |
| Predicate | nacelleSupplier |
P159236
|
FINISHED |
| Object | Spirit AeroSystems |
—
|
NE NERFINISHED |
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: Spirit AeroSystems | Statement: [Rolls-Royce BR725 A1-12, nacelleSupplier, Spirit AeroSystems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nacelleSupplier Context triple: [Rolls-Royce BR725 A1-12, nacelleSupplier, Spirit AeroSystems]
-
A.
hasTurbineSupplier
Indicates that an entity has a specific supplier responsible for providing its turbine(s).
-
B.
chassisSupplier
Indicates that one entity serves as the supplier or provider of the chassis for another entity.
-
C.
aircraftEngineManufacturer
Indicates that one entity is the manufacturer of the aircraft engine used by another entity.
-
D.
propulsionContractor
Indicates that one entity serves as the contractor responsible for providing propulsion systems or propulsion-related services to another entity.
-
E.
reactorTechnologySupplier
Indicates that one entity supplies or provides reactor technology to another entity.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd83a8c08190a01a2ba975690e38 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 4:42 a.m.