Triple
T1434586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paris Summit of 1960 |
E30530
|
entity |
| Predicate | hasCauseOfCollapse |
P26452
|
FINISHED |
| Object | U-2 incident of 1960 |
—
|
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: U-2 incident of 1960 | Statement: [Paris Summit of 1960, hasCauseOfCollapse, U-2 incident of 1960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCauseOfCollapse Context triple: [Paris Summit of 1960, hasCauseOfCollapse, U-2 incident of 1960]
-
A.
hasCauseOfDestruction
Indicates that one entity is the cause or agent responsible for the destruction or damage of another entity.
-
B.
causeOfDownfall
chosen
Indicates a factor, event, or agent that brings about the failure, ruin, or collapse of someone or something.
-
C.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
D.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
E.
collapsedAfter
Indicates that one entity collapsed at some point in time after another specified event or entity’s collapse.
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5ff8dbc81909eafcfc9f2260a22 |
completed | March 1, 2026, 11:04 p.m. |
| PD | Predicate disambiguation | batch_69a4c478f65481909ee716791c663491 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8 p.m.