Triple
T78770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuban Missile Crisis |
E1579
|
entity |
| Predicate | riskLevel |
P3842
|
FINISHED |
| Object | brink of nuclear war |
—
|
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: brink of nuclear war | Statement: [Cuban Missile Crisis, riskLevel, brink of nuclear war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskLevel Context triple: [Cuban Missile Crisis, riskLevel, brink of nuclear war]
-
A.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
B.
revenueLevel
Indicates the relative amount or tier of revenue associated with an entity or activity.
-
C.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
D.
hazardType
Indicates the specific kind or category of hazard associated with an entity or situation.
-
E.
depthRank
Indicates the relative ordering of entities based on how deep or distant they are along a specified depth dimension or hierarchy.
- 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_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. |
| PDg | Predicate description generation | batch_69a24fcf5a88819088c5fa4c08476358 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.