Triple
T20667770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning T.5 |
E507936
|
entity |
| Predicate | flightControl |
P109258
|
FINISHED |
| Object | manual flight controls with hydraulic assistance |
—
|
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: manual flight controls with hydraulic assistance | Statement: [Lightning T.5, flightControl, manual flight controls with hydraulic assistance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightControl Context triple: [Lightning T.5, flightControl, manual flight controls with hydraulic assistance]
-
A.
crewControls
Indicates that a crew has authority over, manages, or directs the operation or behavior of another entity.
-
B.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
C.
aircraftControlType
chosen
Indicates the type or method of control used to operate or direct an aircraft.
-
D.
fuelControl
Indicates a relationship where one entity regulates, manages, or influences the supply or use of fuel for another entity or system.
-
E.
flightMechanic
Indicates that one entity serves as a mechanic responsible for maintaining or repairing the aircraft associated with another entity.
- 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_69e0b4c059bc81908ea762cd73ea4424 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b5c4c4608190ae17da4a59e5ae80 |
completed | April 20, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69e5c03caee881908be4dd25796a03d5 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:44 a.m.