Triple
T18917113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerardo Machado |
E462749
|
entity |
| Predicate | laterPolicyOrientation |
P49036
|
FINISHED |
| Object | increasingly repressive policies |
—
|
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: increasingly repressive policies | Statement: [Gerardo Machado, laterPolicyOrientation, increasingly repressive policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPolicyOrientation Context triple: [Gerardo Machado, laterPolicyOrientation, increasingly repressive policies]
-
A.
laterPolicy
Indicates that one policy occurs or becomes effective after another policy in time.
-
B.
hasPolicyOrientation
chosen
Indicates that one entity (such as an organization, document, or actor) is characterized by or aligned with a particular policy stance, direction, or focus.
-
C.
laterStrategy
Indicates that one strategy or plan occurs or is implemented after another strategy in time.
-
D.
endedPolicy
Indicates that a previously active policy has been brought to an end or terminated.
-
E.
laterConfiguration
Indicates that one configuration occurs after another in time, representing a subsequent or later state relative to a prior configuration.
- 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_69d8dcfdbbb881909964fa5a75bd0b48 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c627724881909cf63c67d64321e8 |
completed | April 20, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.