Triple
T25298484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tor-M2 |
E634281
|
entity |
| Predicate | Tor-M2K |
P158445
|
FINISHED |
| Object | wheeled chassis 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: wheeled chassis variant | Statement: [Tor-M2, Tor-M2K, wheeled chassis variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Tor-M2K Context triple: [Tor-M2, Tor-M2K, wheeled chassis variant]
-
A.
Tor-M2E
Indicates a defensive relationship where the Tor-M2E system detects, tracks, and engages aerial threats such as aircraft, missiles, or drones.
-
B.
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).
-
C.
Typer
Indicates that one entity serves as the type or classification for another entity.
-
D.
trojanMoonOf
Indicates that one celestial body shares an orbit with a larger body at a stable Lagrange point (typically leading or trailing it), acting as a Trojan moon of that body.
-
E.
toolMorphology
Indicates a relationship where one entity’s form, structure, or physical configuration functions as or defines it as a tool for another entity or purpose.
- 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_69f48fd5621481909935d022d9275194 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
| PDg | Predicate description generation | batch_69f46d361c348190b5fdfd805ecde01b |
completed | May 1, 2026, 9:07 a.m. |
Created at: April 21, 2026, 1:22 p.m.