Triple
T25298486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor-M2 |
E634281
|
entity |
| Predicate | Tor-M2DT |
P159096
|
FINISHED |
| Object | Arctic 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: Arctic variant | Statement: [Tor-M2, Tor-M2DT, Arctic variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tor-M2DT Context triple: [Tor-M2, Tor-M2DT, Arctic variant]
-
A.
Tor-M2K
Indicates a defensive relationship where the Tor-M2K system detects, tracks, and engages aerial or missile threats to protect designated assets or areas.
-
B.
Tor-M2KM
Indicates a defensive or protective relationship in which one entity provides surface-to-air missile coverage or air defense support for another.
-
C.
Tor-M2E
Indicates a defensive relationship where the Tor-M2E system detects, tracks, and engages aerial threats such as aircraft, missiles, or drones.
-
D.
Tornado ADV
Indicates that the action or event occurs in the manner of, or under conditions characterized by, a tornado (e.g., violently, turbulently, or with tornado-like intensity).
-
E.
Phantom II Continental
Indicates a relationship where something is identified as, derived from, or associated with the Phantom II Continental model or variant.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 1:22 p.m.