Triple
T31144545
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Saint Takes Over |
E793885
|
entity |
| Predicate | featuresProtagonistAlias |
P46224
|
FINISHED |
| Object | The Saint |
—
|
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 Saint | Statement: [The Saint Takes Over, featuresProtagonistAlias, The Saint]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresProtagonistAlias Context triple: [The Saint Takes Over, featuresProtagonistAlias, The Saint]
-
A.
characterAlias
Indicates that one character is known or referred to by an alternative name or alias.
-
B.
protagonistAlsoKnownAs
chosen
Indicates that an entity serving as a protagonist is alternatively referred to by another name or alias.
-
C.
featuresProtagonistOccupation
Indicates that the work’s main character has a specified occupation or job role.
-
D.
protagonistAlterEgoOf
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
E.
featuresCharacterWith
Indicates that one entity (such as a work or product) includes or presents a particular character as part of its content.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: April 29, 2026, 9:06 p.m.