Triple
T1077000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PAC-1 |
E23861
|
entity |
| Predicate | threatTypeCountered |
P19863
|
FINISHED |
| Object | fixed-wing 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: fixed-wing aircraft | Statement: [PAC-1, threatTypeCountered, fixed-wing aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatTypeCountered Context triple: [PAC-1, threatTypeCountered, fixed-wing aircraft]
-
A.
threatTypeAddressed
chosen
Indicates that a given action, measure, or entity is specifically intended to counter or mitigate a particular type of threat.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threat
Indicates a relationship where one entity expresses or poses potential harm, danger, or negative consequences toward another entity.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
belligerentAgainst
Indicates a hostile or aggressive stance, conflict, or antagonistic behavior directed by one entity against another.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b940d4848190930e73597afd1fcf |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73ba8208190be7f3cef8c18689b |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.