Triple
T6669708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-346A |
E151693
|
entity |
| Predicate | hasDigitalFlightControls |
P18196
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [T-346A, hasDigitalFlightControls, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigitalFlightControls Context triple: [T-346A, hasDigitalFlightControls, true]
-
A.
flyByWire
chosen
Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
-
B.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
C.
flightDeckType
Indicates the specific configuration or design type of a vehicle’s flight deck (cockpit/control area).
-
D.
supercruiseCapability
Indicates that an entity possesses the ability to sustain high-speed travel (typically supersonic) without using afterburners or additional boost mechanisms.
-
E.
hasDigitalSystem
Indicates that an entity possesses, uses, or is equipped with a digital system (such as software, hardware, or an integrated digital platform).
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.