Triple
T27507810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond DA40 |
E694324
|
entity |
| Predicate | avionicsOption |
P34590
|
FINISHED |
| Object | Garmin G1000 glass cockpit |
—
|
NE NERFINISHED |
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: Garmin G1000 glass cockpit | Statement: [Diamond DA40, avionicsOption, Garmin G1000 glass cockpit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: avionicsOption Context triple: [Diamond DA40, avionicsOption, Garmin G1000 glass cockpit]
-
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.
avionicsSupplier
Indicates that one entity supplies avionics systems, components, or related services to another entity.
-
C.
aircraftConfiguration
Indicates the specific arrangement or setup of an aircraft’s components, systems, or features for a given purpose or operating condition.
-
D.
flightDeckFeature
chosen
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
E.
aircraftModification
Indicates a relationship where an aircraft undergoes a change, upgrade, or alteration to its structure, systems, or configuration.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62ef65ca88190b3e3b1c91d668843 |
completed | May 2, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 1:14 p.m.