Triple
T23590564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce Trent 800 |
E582464
|
entity |
| Predicate | notOfferedForAircraft |
P152830
|
FINISHED |
| Object | Boeing 777-300ER |
—
|
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: Boeing 777-300ER | Statement: [Rolls-Royce Trent 800, notOfferedForAircraft, Boeing 777-300ER]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOfferedForAircraft Context triple: [Rolls-Royce Trent 800, notOfferedForAircraft, Boeing 777-300ER]
-
A.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
-
B.
usedOnAircraftName
Indicates that something is employed or applied on an aircraft identified by a specific name.
-
C.
usedInVariantOfAircraft
Indicates that something (such as a component, system, or design feature) is utilized in a particular variant of an aircraft.
-
D.
basedOnAircraft
Indicates that one entity is derived from, modeled after, or otherwise uses a particular aircraft as its basis or primary reference.
-
E.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b03484e4819093d5c14c891f7744 |
completed | April 29, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:42 p.m.