Triple
T31259649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batman: Death and the Maidens |
E797081
|
entity |
| Predicate | featuresDeathOf |
P51826
|
FINISHED |
| Object | Ra’s al Ghul |
—
|
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: Ra’s al Ghul | Statement: [Batman: Death and the Maidens, featuresDeathOf, Ra’s al Ghul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresDeathOf Context triple: [Batman: Death and the Maidens, featuresDeathOf, Ra’s al Ghul]
-
A.
featuresDeath
Indicates that the subject includes, depicts, or involves a death or deaths as a notable element.
-
B.
containsDeathOf
chosen
Indicates that the subject includes, depicts, or involves the death of the referenced entity.
-
C.
facesDeath
Indicates that an entity is confronting, experiencing, or is directly threatened by death or a life-ending situation.
-
D.
legendaryDeath
Indicates a death that is renowned or celebrated in stories or history, often marked by extraordinary circumstances or lasting fame.
-
E.
deathDescribedIn
Indicates that a person's death is documented, narrated, or otherwise detailed within a particular source or description.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a006be462288190ae18e1567e2ad29f |
completed | May 10, 2026, 11:28 a.m. |
| PD | Predicate disambiguation | batch_6a0069e7a424819098d38458c3823605 |
completed | May 10, 2026, 11:20 a.m. |
Created at: April 29, 2026, 9:12 p.m.