Triple
T4226936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panavia Tornado |
E94480
|
entity |
| Predicate | Tornado IDS |
P55431
|
FINISHED |
| Object | interdictor/strike variant |
—
|
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: interdictor/strike variant | Statement: [Panavia Tornado, Tornado IDS, interdictor/strike variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tornado IDS Context triple: [Panavia Tornado, Tornado IDS, interdictor/strike variant]
-
A.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
B.
typicalStormType
Indicates the kind of storm that is most commonly or characteristically associated with a given context or location.
-
C.
defensiveSystem
Indicates a system or mechanism whose primary function is to protect, guard, or defend an entity against threats or attacks.
-
D.
securityCollaboration
Indicates a cooperative relationship in which entities work together to plan, implement, or maintain security measures, policies, or defenses.
-
E.
targetedInfrastructure
Indicates that an entity deliberately selected and acted against a specific piece of infrastructure as the focus of its operation or attack.
- F. None of above. chosen
Provenance (4 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e5003008190834726e46df3ee9b |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:04 p.m.