Triple
T31357881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Humanoids |
E799784
|
entity |
| Predicate | hasMainAntagonistGroup |
P17627
|
FINISHED |
| Object | the Humanoids |
—
|
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: the Humanoids | Statement: [The Humanoids, hasMainAntagonistGroup, the Humanoids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAntagonistGroup Context triple: [The Humanoids, hasMainAntagonistGroup, the Humanoids]
-
A.
hasAntagonistGroup
chosen
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
B.
hasProtagonistGroup
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
C.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
-
D.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
E.
isCentralAntagonist
Indicates that an entity serves as the primary opposing force or main villain driving conflict against the protagonist or central characters.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0018cf6ebc8190aee6288788d0067e |
completed | May 10, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_6a001855e8588190a65840485473cf8b |
completed | May 10, 2026, 5:32 a.m. |
Created at: April 29, 2026, 9:17 p.m.