Triple
T25354118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EA-18G Growler |
E635772
|
entity |
| Predicate | airframeSharedWith |
P52744
|
FINISHED |
| Object | F/A-18F Super Hornet |
—
|
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: F/A-18F Super Hornet | Statement: [EA-18G Growler, airframeSharedWith, F/A-18F Super Hornet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airframeSharedWith Context triple: [EA-18G Growler, airframeSharedWith, F/A-18F Super Hornet]
-
A.
airframeCommonalityWith
chosen
Indicates that two aircraft share the same or highly similar structural design and components in their airframes.
-
B.
sharesAircraftWith
Indicates that two or more entities use, operate, or are associated with the same aircraft.
-
C.
airfieldSharedWith
Indicates that two or more entities use the same airfield facilities or infrastructure for their operations.
-
D.
airframe
Indicates that an entity is the structural framework or body of an aircraft associated with another entity (such as a specific model, component, or system).
-
E.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49dfedae88190a02f10196ef45ffa |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:34 p.m.