Triple
T2109247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soviet Air Defense Forces |
E42465
|
entity |
| Predicate | peakEquipment |
P34816
|
FINISHED |
| Object | thousands of SAM launchers |
—
|
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: thousands of SAM launchers | Statement: [Soviet Air Defense Forces, peakEquipment, thousands of SAM launchers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peakEquipment Context triple: [Soviet Air Defense Forces, peakEquipment, thousands of SAM launchers]
-
A.
recommendedEquipment
Indicates that one entity suggests or endorses another entity as suitable equipment to be used in a particular context or activity.
-
B.
peakService
Indicates that the service is operating during its highest-demand or peak usage period.
-
C.
notableGroundEquipment
Indicates that there is ground-based equipment at or associated with an entity that is considered significant or noteworthy in some context.
-
D.
safetyEquipment
Indicates that one entity serves as safety equipment used to protect another entity from harm or danger.
-
E.
toolIn
Indicates that one entity is a tool or instrument used in or associated with another entity or context.
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae1bacc8190beffc9d0470e9190 |
completed | March 7, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:43 p.m.