Triple
T1371628
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powers incident |
E30123
|
entity |
| Predicate | airDefenseSystemInvolved |
P27065
|
FINISHED |
| Object | Soviet surface-to-air missiles |
—
|
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: Soviet surface-to-air missiles | Statement: [Powers incident, airDefenseSystemInvolved, Soviet surface-to-air missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airDefenseSystemInvolved Context triple: [Powers incident, airDefenseSystemInvolved, Soviet surface-to-air missiles]
-
A.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
-
B.
airForceInvolved
Indicates that an air force participates in, contributes to, or is otherwise involved in a specified event, operation, or situation.
-
C.
nearMilitaryInstallation
Indicates that one entity is located in close physical proximity to a military installation or facility.
-
D.
defenseResult
Indicates the outcome or consequence of a defensive action or strategy in response to an attack or threat.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2f314c081909c0ab80397d96abb |
completed | March 1, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69a4befb08b88190be966fa1aadd4bcd |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4bfc2134c81909cbaaa151d96e9a8 |
completed | March 1, 2026, 10:37 p.m. |
Created at: March 1, 2026, 7:57 p.m.