Triple
T5789180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tale of Jemima Puddle-Duck |
E128348
|
entity |
| Predicate | includesAntagonist |
P32100
|
FINISHED |
| Object | a cunning fox |
—
|
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: a cunning fox | Statement: [The Tale of Jemima Puddle-Duck, includesAntagonist, a cunning fox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAntagonist Context triple: [The Tale of Jemima Puddle-Duck, includesAntagonist, a cunning fox]
-
A.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
-
B.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
C.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
D.
hasVillain
chosen
Indicates that one entity is the villain or primary antagonist associated with another entity.
-
E.
primaryAntagonistType
Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a53d0148190bdebc4f5609939ac |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.