Triple
T20515903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lightning F.1 |
E503680
|
entity |
| Predicate | airDefenseNetworkRole |
P37652
|
FINISHED |
| Object | quick reaction alert |
—
|
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: quick reaction alert | Statement: [Lightning F.1, airDefenseNetworkRole, quick reaction alert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airDefenseNetworkRole Context triple: [Lightning F.1, airDefenseNetworkRole, quick reaction alert]
-
A.
airDefenseSystem
Indicates a defensive military system designed to detect, track, and engage airborne threats such as aircraft or missiles.
-
B.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
-
C.
airDefenseArmament
Indicates the weapons or systems specifically equipped on an entity for defending against aerial threats such as aircraft or missiles.
-
D.
airDefenseResponsibility
chosen
Indicates that an entity has the duty or authority to protect a specified area, asset, or force against airborne threats.
-
E.
airDefenseSystemInvolved
Indicates that an air defense system participates in or is used during a specific event, operation, or engagement.
- 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_69e0b4b2aa788190ae9eb37c1d73b1f1 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69f41eee481908121e54c7bd691ca |
completed | April 20, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e59fdb7ad88190924176c32a195db3 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:36 a.m.