Triple
T18780642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solex Agitator |
E459244
|
entity |
| Predicate | motivationForAntagonist |
P91485
|
FINISHED |
| Object | leverage energy monopoly and power |
—
|
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: leverage energy monopoly and power | Statement: [Solex Agitator, motivationForAntagonist, leverage energy monopoly and power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motivationForAntagonist Context triple: [Solex Agitator, motivationForAntagonist, leverage energy monopoly and power]
-
A.
missionOfAntagonist
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
-
B.
characterMotivation
chosen
Indicates the underlying reasons, desires, or goals that drive a character’s actions and decisions within a narrative.
-
C.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
D.
antagonistActionOf
Indicates that one entity performs an action in opposition or hostility toward another entity, acting as its antagonist.
-
E.
motivationFor
Indicates that one entity serves as the reason, drive, or incentive behind another entity’s action, state, or occurrence.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933ee89481908b647802961e4519 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.