Triple
T28207751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Devil’s Disciple (stage role) |
E717077
|
entity |
| Predicate | hasTitleCharacterOf |
P46756
|
FINISHED |
| Object | The Devil’s Disciple |
—
|
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: The Devil’s Disciple | Statement: [The Devil’s Disciple (stage role), hasTitleCharacterOf, The Devil’s Disciple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTitleCharacterOf Context triple: [The Devil’s Disciple (stage role), hasTitleCharacterOf, The Devil’s Disciple]
-
A.
hasTitleCharacterFrom
Indicates that a work has a title that includes or is derived from a specific character.
-
B.
hasTitleCharacterAction
Indicates that a work’s title explicitly references or is derived from an action performed by a character within that work.
-
C.
hasTitleLetter
Indicates that an entity possesses a specific letter or character within its title.
-
D.
hasMainTitleCharacter
Indicates that a work’s primary or main title is centered on, derived from, or explicitly names a particular character.
-
E.
hasTitleCharacterRelation
chosen
Indicates a relationship where a title (such as a work or publication) is associated with or linked to a specific character appearing in it.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 10:36 p.m.