Triple
T38152497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAE Systems Hawk T2 |
E952791
|
entity |
| Predicate | hasFlightControls |
P109258
|
FINISHED |
| Object | fly-by-wire-like training environment |
—
|
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: fly-by-wire-like training environment | Statement: [BAE Systems Hawk T2, hasFlightControls, fly-by-wire-like training environment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFlightControls Context triple: [BAE Systems Hawk T2, hasFlightControls, fly-by-wire-like training environment]
-
A.
aircraftControlType
chosen
Indicates the type or method of control used to operate or direct an aircraft.
-
B.
supportsFlightMode
Indicates that an entity provides or is compatible with a flight mode feature or operation.
-
C.
hasAttitudeControl
Indicates that an entity possesses the capability or system to control and adjust its orientation or attitude in space.
-
D.
crewControls
Indicates that a crew has authority over, manages, or directs the operation or behavior of another entity.
-
E.
hasTakeoffAndLandingCapability
Indicates that an entity possesses the ability to both take off and land, typically under its own operational power or design.
- 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_69f76f0a67f4819080c492f61d688fcc |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:21 p.m.