Triple
T3747613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce LiftSystem |
E81244
|
entity |
| Predicate | exhaustVectoring |
P19997
|
FINISHED |
| Object | three-bearing swivel nozzle |
—
|
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: three-bearing swivel nozzle | Statement: [Rolls-Royce LiftSystem, exhaustVectoring, three-bearing swivel nozzle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exhaustVectoring Context triple: [Rolls-Royce LiftSystem, exhaustVectoring, three-bearing swivel nozzle]
-
A.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
-
B.
emissionsControl
Indicates a relationship where one entity regulates, limits, or manages the release of emissions produced by another entity or process.
-
C.
drivingForce
Indicates a causal influence or motivating factor that propels or significantly shapes another process, event, or outcome.
-
D.
turbochargedVariant
Indicates that one entity is a turbocharged version or configuration of another entity.
-
E.
thrustVectorControl
chosen
Indicates the capability to direct or adjust the direction of thrust from a propulsion system to control an object's attitude or trajectory.
- 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_69ad8b19b7b08190a6188804e99c53e9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb6ac5ac8190934ec1a6c887a8f5 |
completed | March 8, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69adc04adebc819088d7f36d0ac343a6 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.