Triple
T31024971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxcart |
E790543
|
entity |
| Predicate | codeNameOfAircraftVariant |
P112364
|
FINISHED |
| Object | A-12 |
—
|
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: A-12 | Statement: [Oxcart, codeNameOfAircraftVariant, A-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeNameOfAircraftVariant Context triple: [Oxcart, codeNameOfAircraftVariant, A-12]
-
A.
specificCarrierAircraftVariant
Indicates that one aircraft variant is a specific version designed or adapted for carrier-based operations of another, more general aircraft variant.
-
B.
subjectAircraftNotableVariant
Indicates that the subject aircraft has a notable or significant variant related to it.
-
C.
natoReportingNameOfBaseAircraft
Indicates that one entity is the NATO reporting name assigned to the other entity, which is the original (base) aircraft model.
-
D.
airForceVariant
Indicates that one entity is a version or model of something specifically adapted for use by an air force.
-
E.
aircraftNamedNATOCode
chosen
Indicates that an aircraft is designated or referred to by a specific NATO reporting name or code.
- 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ef92308190903a54fc74233269 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:58 p.m.