Triple
T16025146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jorge Ubico |
E388697
|
entity |
| Predicate | repressionTarget |
P40675
|
FINISHED |
| Object | labor organizers |
—
|
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: labor organizers | Statement: [Jorge Ubico, repressionTarget, labor organizers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repressionTarget Context triple: [Jorge Ubico, repressionTarget, labor organizers]
-
A.
oppositionTargeted
chosen
Indicates that an action or strategy is specifically directed against or aimed at an opposing party, group, or viewpoint.
-
B.
repressedDissent
Indicates that one party has actively suppressed or stifled opposition, criticism, or disagreement from another party or group.
-
C.
perpetratorsTargeted
Indicates that the perpetrators intentionally selected or focused on specific targets for their actions.
-
D.
notableRepressionEvent
Indicates a significant instance in which an entity engaged in or experienced systematic repression, such as suppression of rights, freedoms, or dissent.
-
E.
targetedRegime
Indicates that an entity intentionally directed actions, policies, or operations against a particular governing regime.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e1826a4f7c8190aba6d4f1075141b0 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:55 a.m.