Triple
T29185803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephen Byerley |
E739864
|
entity |
| Predicate | antagonisticFor |
P18963
|
FINISHED |
| Object | anti-robot political opponents |
—
|
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: anti-robot political opponents | Statement: [Stephen Byerley, antagonisticFor, anti-robot political opponents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antagonisticFor Context triple: [Stephen Byerley, antagonisticFor, anti-robot political opponents]
-
A.
antagonisticInteractionWith
Indicates a hostile or oppositional interaction in which one entity acts against, harms, or obstructs another.
-
B.
antagonisticArc
Indicates a relationship in which one entity consistently opposes, harms, or works against another over the course of a conflict or storyline.
-
C.
antagonistOf
chosen
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
D.
opposesEffectOf
Indicates that one entity counteracts, reduces, or nullifies the effect produced by another entity.
-
E.
antagonistActionOf
Indicates that one entity performs an action in opposition or hostility toward another entity, acting as its antagonist.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6638722fc819098f18314dfa88a6c |
completed | May 2, 2026, 8:50 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 11:59 a.m.