Triple
T31949253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RP-9 radar |
E815734
|
entity |
| Predicate | usedInConflictEra |
P119523
|
FINISHED |
| Object | Cold War air defense operations |
—
|
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: Cold War air defense operations | Statement: [RP-9 radar, usedInConflictEra, Cold War air defense operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInConflictEra Context triple: [RP-9 radar, usedInConflictEra, Cold War air defense operations]
-
A.
conflictEra
Indicates that two entities are associated with the same historical period or era of conflict.
-
B.
usedDuringEraOf
chosen
Indicates that something was in use or actively employed during the time period or historical era associated with another entity.
-
C.
usedByDuringConflict
Indicates that one entity made practical use of another entity specifically in the context of a particular conflict or war.
-
D.
usedInWar
Indicates that something (such as a resource, technology, or strategy) was employed as part of military activities or conflict in a war.
-
E.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 1, 2026, 12:07 a.m.