Triple
T32613118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardians |
E833711
|
entity |
| Predicate | primaryAntagonistPortrayedBy |
P113106
|
FINISHED |
| Object | Karel Roden |
E197247
|
NE 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: Karel Roden | Statement: [Guardians, primaryAntagonistPortrayedBy, Karel Roden]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryAntagonistPortrayedBy Context triple: [Guardians, primaryAntagonistPortrayedBy, Karel Roden]
-
A.
mainAntagonistPortrayedBy
chosen
Indicates that the person is the primary actor who plays the main antagonist character in a work.
-
B.
primaryAntagonistType
Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
-
C.
antagonistActorRole
Indicates that an actor plays the role of an antagonist in a given work or context.
-
D.
primaryAntagonists
Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
-
E.
leadAntagonistCharacter
Indicates that one character serves as the primary opposing or villainous force in relation to another entity in the narrative.
- F. None of above.
Provenance (4 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34daa296a48190a4241be550010df8 |
completed | June 19, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_6a0379f0cbe481909b4b8fc6cbe297f0 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:06 a.m.