Triple
T3747615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolls-Royce LiftSystem |
E81244
|
entity |
| Predicate | providesControl |
P30853
|
FINISHED |
| Object | roll control in STOVL mode |
—
|
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: roll control in STOVL mode | Statement: [Rolls-Royce LiftSystem, providesControl, roll control in STOVL mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesControl Context triple: [Rolls-Royce LiftSystem, providesControl, roll control in STOVL mode]
-
A.
canControl
chosen
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
B.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
C.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
-
D.
usedToControl
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
-
E.
hasControlCab
Indicates that an entity is equipped with or includes a control cab used for operating or controlling it.
- 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.