Triple
T36369638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-2A Greyhound |
E895718
|
entity |
| Predicate | airframeRelationship |
P52744
|
FINISHED |
| Object | shares wing with E-2 Hawkeye |
—
|
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: shares wing with E-2 Hawkeye | Statement: [C-2A Greyhound, airframeRelationship, shares wing with E-2 Hawkeye]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airframeRelationship Context triple: [C-2A Greyhound, airframeRelationship, shares wing with E-2 Hawkeye]
-
A.
airframeDerivedFrom
Indicates that one airframe design is derived or developed from another pre-existing airframe design.
-
B.
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).
-
C.
airframeConstruction
Indicates the method or structural approach used to build an aircraft’s main body and supporting framework.
-
D.
airframeCommonalityWith
chosen
Indicates that two aircraft share the same or highly similar structural design and components in their airframes.
-
E.
airframeNumber
Indicates the unique identifying number assigned to a specific aircraft’s structural frame within a fleet or system.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.