Triple
T37810125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Apocalypse |
E942617
|
entity |
| Predicate | featuresPerformerKnownFor |
P204398
|
FINISHED |
| Object | genre cinema |
—
|
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: genre cinema | Statement: [My Apocalypse, featuresPerformerKnownFor, genre cinema]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresPerformerKnownFor Context triple: [My Apocalypse, featuresPerformerKnownFor, genre cinema]
-
A.
featuresPerformerCameo
Indicates that the subject includes a brief, special appearance by a performer who is not part of the main cast or lineup.
-
B.
featuresPerformerType
Indicates that something includes or highlights a performer of a specified type (e.g., musician, actor, or other performance role).
-
C.
actorKnownFor
Indicates that an actor is widely recognized or notable for a particular work, role, or contribution.
-
D.
laterKnownFor
Indicates that an entity became recognized or notable for something at a later time than the context or event currently being referred to.
-
E.
nowKnownFor
Indicates that an entity is currently recognized or notable for a particular role, attribute, achievement, or association.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c84ecbc81908232e5215355f43b |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.