Triple
T1843436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panavia Tornado GR4 |
E41228
|
entity |
| Predicate | avionicsUpgrade |
P5243
|
FINISHED |
| Object | GPS navigation |
—
|
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: GPS navigation | Statement: [Panavia Tornado GR4, avionicsUpgrade, GPS navigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avionicsUpgrade Context triple: [Panavia Tornado GR4, avionicsUpgrade, GPS navigation]
-
A.
avionics
Indicates that an entity is related to the electronic systems used to control, monitor, or assist the operation of aircraft or spacecraft.
-
B.
aircraftModification
chosen
Indicates a relationship where an aircraft undergoes a change, upgrade, or alteration to its structure, systems, or configuration.
-
C.
avionicsSupplier
Indicates that one entity supplies avionics systems, components, or related services to another entity.
-
D.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
E.
flyByWire
Indicates a control relationship where an aircraft’s control surfaces are operated by electronic signals rather than direct mechanical linkage from the pilot.
- 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_69a88648cd44819093303206d96d76ad |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafdb0d2c8190a67f584e67979fa3 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.