Triple

T24168007
Position Surface form Disambiguated ID Type / Status
Subject Vought E599046 entity
Predicate A-7 Corsair IIRole P53999 FINISHED
Object carrier-capable subsonic attack aircraft 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: carrier-capable subsonic attack aircraft | Statement: [Vought, A-7 Corsair IIRole, carrier-capable subsonic attack aircraft]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: A-7 Corsair IIRole
Context triple: [Vought, A-7 Corsair IIRole, carrier-capable subsonic attack aircraft]
  • A. basedAircraftRole
    Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
  • B. notableAircraftRole chosen
    Indicates that an aircraft is notably associated with performing a particular role or function.
  • C. carriedAircraftRole
    Indicates the functional role or mission type that an aircraft serves when it is carried by another platform (such as a ship or larger aircraft).
  • D. PC-6Role
    Indicates that an entity participates in or is assigned a specific role within a PC-6 (Pilatus PC-6 aircraft)–related context or activity.
  • E. aircraftRoleSpecialization
    Indicates that one aircraft role is a more specific, specialized form of another, more general aircraft role.
  • 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_69e288cbd62881909de32ca64a70c17b completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27c9ddfcc819096697a844b300cce completed April 29, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69f1c42f942c8190b103ff29a60fef34 completed April 29, 2026, 8:41 a.m.
Created at: April 17, 2026, 11:33 p.m.