Triple
T38489520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Utah |
E918014
|
entity |
| Predicate | mainAntagonistRelationship |
P81119
|
FINISHED |
| Object | Bodhi |
—
|
NE NERFINISHED |
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: Bodhi | Statement: [Johnny Utah, mainAntagonistRelationship, Bodhi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainAntagonistRelationship Context triple: [Johnny Utah, mainAntagonistRelationship, Bodhi]
-
A.
relationshipWithAntagonist
Indicates a relationship or connection that an entity has with an opposing or adversarial figure in a narrative or context.
-
B.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
-
C.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
D.
primaryAntagonists
chosen
Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
-
E.
antagonistAlterEgoOf
Indicates that one entity serves as the primary opposing force or enemy of another entity’s alternate identity or secret persona.
- 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_69f76e9894208190a129a553a60ca58c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:31 p.m.