Triple
T25707615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mystery of Holly Lane |
E644635
|
entity |
| Predicate | hasRecurringVillainOrAntagonist |
P183323
|
FINISHED |
| Object | Mr Goon |
—
|
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: Mr Goon | Statement: [The Mystery of Holly Lane, hasRecurringVillainOrAntagonist, Mr Goon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringVillainOrAntagonist Context triple: [The Mystery of Holly Lane, hasRecurringVillainOrAntagonist, Mr Goon]
-
A.
hasVillain
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
B.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
-
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.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
-
E.
recurringEnemyOf
chosen
Indicates that one entity repeatedly serves as an adversary or opponent to another over multiple encounters or events.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 21, 2026, 9:06 p.m.