Triple
T36965448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Sunderland |
E914415
|
entity |
| Predicate | antagonistEmbodiment |
P187455
|
FINISHED |
| Object | Pyramid Head |
—
|
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: Pyramid Head | Statement: [James Sunderland, antagonistEmbodiment, Pyramid Head]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antagonistEmbodiment Context triple: [James Sunderland, antagonistEmbodiment, Pyramid Head]
-
A.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
B.
antagonistStatus
Indicates that an entity holds an opposing or adversarial role, often acting as the main source of conflict relative to another entity or objective.
-
C.
antagonistActorRole
Indicates that an actor plays the role of an antagonist in a given work or context.
-
D.
antagonistAlterEgoOf
Indicates that one entity serves as the primary opposing force or enemy of another entity’s alternate identity or secret persona.
-
E.
antagonistAttribute
Indicates that an entity possesses a characteristic or role specifically associated with being an antagonist in a narrative or conflict.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:14 p.m.