Triple
T16639375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AN/APY-1 |
E404288
|
entity |
| Predicate | natoDesignationContext |
P18385
|
FINISHED |
| Object | used on NATO E-3A AWACS 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: used on NATO E-3A AWACS aircraft | Statement: [AN/APY-1, natoDesignationContext, used on NATO E-3A AWACS aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natoDesignationContext Context triple: [AN/APY-1, natoDesignationContext, used on NATO E-3A AWACS aircraft]
-
A.
NATOcode
Indicates that there is a specified NATO (North Atlantic Treaty Organization) code assigned to or associated with an entity.
-
B.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
C.
hasNATOContext
Indicates that something is related to, influenced by, or situated within the context of NATO, its activities, policies, or structures.
-
D.
airForceDesignation
Indicates that one entity is the official designation or code assigned to something by an air force.
-
E.
NATODesignation
chosen
Indicates that one entity is the official name or code assigned to another entity by NATO for identification or classification purposes.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37acff38081908c8044936b794ce0 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:18 a.m.