Triple
T2881649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juanita Castro |
E59409
|
entity |
| Predicate | emigration |
P195
|
FINISHED |
| Object | emigrated from Cuba to the United States |
—
|
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: emigrated from Cuba to the United States | Statement: [Juanita Castro, emigration, emigrated from Cuba to the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emigration Context triple: [Juanita Castro, emigration, emigrated from Cuba to the United States]
-
A.
estimatedEmigrants
Indicates the estimated number of people who have left a place or country to live elsewhere.
-
B.
immigratedTo
chosen
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
C.
hasNotableEmigrant
Indicates that an entity has at least one emigrant who is considered notable or significant in some recognized way.
-
D.
yearOfEmigration
Indicates the specific year in which an entity permanently left its country or place of origin to settle elsewhere.
-
E.
usedToRestrictEmigrationFrom
Indicates that something was employed as a means to limit or control people leaving a particular place or country.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe02aa5948190a2e0bd9168232bd5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.