Triple
T38129734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negaduck (Darkwing Duck) (voice) |
E952183
|
entity |
| Predicate | portraysRoleInStory |
P42552
|
FINISHED |
| Object | primary antagonist |
—
|
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: primary antagonist | Statement: [Negaduck (Darkwing Duck) (voice), portraysRoleInStory, primary antagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portraysRoleInStory Context triple: [Negaduck (Darkwing Duck) (voice), portraysRoleInStory, primary antagonist]
-
A.
roleInStories
chosen
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
B.
portraysCharacterIn
Indicates that one entity depicts or represents a particular character within a work, such as a film, show, or other narrative medium.
-
C.
portraysRoleTrait
Indicates that one entity depicts or represents a particular role or character trait of another entity.
-
D.
portraysMainCharacter
Indicates that one entity depicts or represents another entity as the primary or central character in a work or narrative.
-
E.
narrativeRoleInSeries
Indicates the specific narrative function or role an entity plays within a particular series or serialized work.
- 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_69f76f083548819082bd2bbf53c79e8e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:21 p.m.