Triple
T15408718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | God Forgives, I Don’t |
E368527
|
entity |
| Predicate | mainPerformerPersona |
P85537
|
FINISHED |
| Object | larger-than-life |
—
|
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: larger-than-life | Statement: [God Forgives, I Don’t, mainPerformerPersona, larger-than-life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerPersona Context triple: [God Forgives, I Don’t, mainPerformerPersona, larger-than-life]
-
A.
stagePersonaOf
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
E.
typicalPerformerRoleType
chosen
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03ea4f13c819085d26fd32b5dca6f |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:20 a.m.