Triple
T22974450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deadpool (Brian Posehn co-written run) |
E571275
|
entity |
| Predicate | hasProtagonistAlignment |
P47185
|
FINISHED |
| Object | antihero |
—
|
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: antihero | Statement: [Deadpool (Brian Posehn co-written run), hasProtagonistAlignment, antihero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistAlignment Context triple: [Deadpool (Brian Posehn co-written run), hasProtagonistAlignment, antihero]
-
A.
protagonistAllegiance
chosen
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
B.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
C.
hasBlackProtagonist
Indicates that the work features a main character whose racial identity is Black.
-
D.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
-
E.
hasChildProtagonist
Indicates that the work features a child as its main or central character.
- 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_69e245b2c6548190a0e4c7f2f7df2d48 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182350b448190a34e5fa0167fd964 |
completed | April 29, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9101f48190a06c69dff26c6441 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:48 p.m.