Triple
T16567080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northrop Grumman C-2 Greyhound |
E402488
|
entity |
| Predicate | variant |
P4680
|
FINISHED |
| Object | C-2A |
E895718
|
NE 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: C-2A | Statement: [Northrop Grumman C-2 Greyhound, variant, C-2A]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: C-2A Context triple: [Northrop Grumman C-2 Greyhound, variant, C-2A]
-
A.
C-2A
chosen
The C-2A is a twin-engine, high-wing cargo aircraft used by the U.S. Navy primarily for carrier onboard delivery (COD) missions.
-
B.
C-21A
The C-21A is a U.S. military transport and medical evacuation aircraft derived from the Learjet 35 business jet.
-
C.
C-20
C-20 is the NATO reporting name for the Gulfstream C-20, a military transport and VIP aircraft derived from the Gulfstream III business jet.
-
D.
C-2
C-2 is a commuter rail line within the Cercanías Madrid network that connects central Madrid with its surrounding metropolitan areas.
-
E.
C-28
C-28 is a mountain road in the Catalan Pyrenees that connects the Val d'Aran with the Pallars Sobirà region via the Port de la Bonaigua pass.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35772255881909f737da89bcd06b8 |
completed | April 18, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006ee3dcbc819087ea66b262585232 |
completed | May 10, 2026, 11:41 a.m. |
Created at: April 10, 2026, 5:16 a.m.