Triple
T35500132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count Duckula |
E1025974
|
entity |
| Predicate | hasMainProtagonistTrait |
P203878
|
FINISHED |
| Object | cowardly |
—
|
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: cowardly | Statement: [Count Duckula, hasMainProtagonistTrait, cowardly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainProtagonistTrait Context triple: [Count Duckula, hasMainProtagonistTrait, cowardly]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
hasSpiritProtagonist
Indicates that the primary or central character in a narrative is a spirit or non-corporeal being.
-
D.
hasHumanProtagonists
Indicates that the primary characters driving the narrative are human beings rather than non-human entities.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
- F. None of above. chosen
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_69f76dfc9c60819089c4217d93922615 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0235be932081908857bc3a77c27e7d |
completed | May 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a022c865dec81909e02b2f330e987e6 |
completed | May 11, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_6a0235bd9f5481908d9a173517211119 |
completed | May 11, 2026, 8:02 p.m. |
Created at: May 3, 2026, 4:04 p.m.