Triple
T5820651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright Flyer (1903) |
E129097
|
entity |
| Predicate | flightControlSystem |
P21084
|
FINISHED |
| Object | three-axis control |
—
|
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-axis control | Statement: [Wright Flyer (1903), flightControlSystem, three-axis control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flightControlSystem Context triple: [Wright Flyer (1903), flightControlSystem, three-axis control]
-
A.
controlsPhaseOfFlight
Indicates that one entity has authority over or manages a specific phase of another entity’s flight operation.
-
B.
flyByWire
Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
-
C.
attitudeControlMethod
chosen
Indicates the technique or mechanism used to control or adjust the orientation or pointing direction of an object (such as a vehicle or device).
-
D.
guidanceControl
Indicates that one entity directs, manages, or influences the behavior or decisions of another through guidance or control.
-
E.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.