Triple
T26700745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bruce Nolan |
E673147
|
entity |
| Predicate | misusesPowersFor |
P158592
|
FINISHED |
| Object | petty revenge |
—
|
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: petty revenge | Statement: [Bruce Nolan, misusesPowersFor, petty revenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: misusesPowersFor Context triple: [Bruce Nolan, misusesPowersFor, petty revenge]
-
A.
abusesPowerOver
chosen
Indicates that one entity misuses their authority or control to unfairly dominate, exploit, or harm another entity.
-
B.
exercisedPowerWith
Indicates that one entity actively used or exerted power in conjunction with another entity, implying a shared or coordinated exercise of authority or influence.
-
C.
exercisedPowerOver
Indicates that one entity exerted control, influence, or authority over another entity.
-
D.
usesPoliticalPowerFor
Indicates that an entity employs its political authority or influence to achieve, support, or advance a specified purpose, goal, or outcome.
-
E.
exercisedPowerFrom
Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:31 a.m.