Triple
T507093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuba |
E10524
|
entity |
| Predicate | revolutionVictoryDate |
P4401
|
FINISHED |
| Object | 1959-01-01 |
—
|
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: 1959-01-01 | Statement: [Cuba, revolutionVictoryDate, 1959-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revolutionVictoryDate Context triple: [Cuba, revolutionVictoryDate, 1959-01-01]
-
A.
revolutionVictoryYear
chosen
Indicates the year in which a revolution achieved victory or successfully overthrew the existing regime.
-
B.
liberationEvent
Indicates an event in which an entity is freed from control, confinement, or oppression by another entity or condition.
-
C.
uprisingDate
Indicates the date on which an uprising or rebellion occurred or began.
-
D.
victoryIn
Indicates that one entity achieves a win or success in a specific contest, event, or competitive context involving another entity.
-
E.
conquestYear
Indicates the year in which one entity successfully conquered or took control over another entity.
- 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_69a2e848adf881908e5e04f7af030093 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f14c83f08190b1028f4929866db4 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfce7a08190a408bc019de60d5d |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.