Triple
T12876068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Popular Socialist Party |
E307968
|
entity |
| Predicate | hadGoal |
P107402
|
FINISHED |
| Object | establishment of socialism in 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: establishment of socialism in Cuba | Statement: [Popular Socialist Party, hadGoal, establishment of socialism in Cuba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadGoal Context triple: [Popular Socialist Party, hadGoal, establishment of socialism in Cuba]
-
A.
hasGoalYear
Indicates that an entity is associated with a specific target year by which a goal or objective is intended to be achieved.
-
B.
goalIn
Indicates that one entity’s objective, aim, or intended outcome is located within, directed toward, or achieved inside another entity or context.
-
C.
formerGoal
Indicates that an entity previously had a particular goal or objective, but no longer has it.
-
D.
hasPlanningGoal
Indicates that an entity is associated with, or directed toward achieving, a specific planning objective or target state.
-
E.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
- 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_69d7bdf69bc48190af6c2621f28ca351 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97c7f91d08190aac2f6419d3ba992 |
completed | April 10, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69d96fa55b888190ab1612e93c41aec4 |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d97c7d0598819080cab0a2314bc106 |
completed | April 10, 2026, 10:41 p.m. |
Created at: April 9, 2026, 5:38 p.m.