Triple
T78780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuban Missile Crisis |
E1579
|
entity |
| Predicate | USResponse |
P1128
|
FINISHED |
| Object | naval quarantine of Cuba |
—
|
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: naval quarantine of Cuba | Statement: [Cuban Missile Crisis, USResponse, naval quarantine of Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: USResponse Context triple: [Cuban Missile Crisis, USResponse, naval quarantine of Cuba]
-
A.
wasResponseTo
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
B.
enactedInResponseTo
chosen
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
-
C.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
D.
USViewers
Indicates the number or set of viewers located in the United States who watched or were exposed to a particular piece of content or event.
-
E.
hasSpokenAbout
Indicates that one entity has verbally expressed, discussed, or mentioned another entity or topic.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.