Triple
T38477580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyranny |
E915586
|
entity |
| Predicate | choiceConsequence |
P14171
|
FINISHED |
| Object | changes in political landscape |
—
|
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: changes in political landscape | Statement: [Tyranny, choiceConsequence, changes in political landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: choiceConsequence Context triple: [Tyranny, choiceConsequence, changes in political landscape]
-
A.
consequenceOfInfluence
Indicates that one event, state, or condition occurs as a result of the influence or impact exerted by another.
-
B.
hasConsequence
Indicates that one event, action, or condition leads to or results in another as its outcome or effect.
-
C.
decisionEffect
chosen
Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
-
D.
consequenceInText
Indicates that one event, action, or state is presented in the text as a consequence or result of another.
-
E.
consequenceOfQuest
Indicates that an event, state, or outcome occurs as a direct result of completing or progressing in a specific quest.
- 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_69f76e8ff5cc8190a88803369183845e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.