Triple
T857091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BAE Systems Hawk T1 |
E18515
|
entity |
| Predicate | cockpitConfiguration |
P3544
|
FINISHED |
| Object | tandem seating |
—
|
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: tandem seating | Statement: [BAE Systems Hawk T1, cockpitConfiguration, tandem seating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cockpitConfiguration Context triple: [BAE Systems Hawk T1, cockpitConfiguration, tandem seating]
-
A.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
B.
cockpitType
chosen
Indicates the specific configuration or style of cockpit associated with an entity (e.g., vehicle or aircraft).
-
C.
wingConfiguration
Indicates how the wings of an aircraft or creature are arranged or structured relative to its body and to each other.
-
D.
aircraftModification
Indicates a relationship where an aircraft undergoes a change, upgrade, or alteration to its structure, systems, or configuration.
-
E.
aircraftConfigurationProduced
Indicates that a specific aircraft configuration has been manufactured or produced.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac4d47508190b48d944aa2d881bf |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.