Triple
T29160202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Play Dead (stage show) |
E739163
|
entity |
| Predicate | coCreatorOccupation |
P166373
|
FINISHED |
| Object | Raymond Teller – magician |
—
|
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: Raymond Teller – magician | Statement: [Play Dead (stage show), coCreatorOccupation, Raymond Teller – magician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coCreatorOccupation Context triple: [Play Dead (stage show), coCreatorOccupation, Raymond Teller – magician]
-
A.
coCreator
Indicates that two or more entities jointly created or produced something together.
-
B.
creatorOccupation
Indicates the professional role or job that the creator of an entity holds or held.
-
C.
coCreatorNationality
Indicates that two or more co-creators share the same national origin or nationality in the context of their joint work or collaboration.
-
D.
creativeContributor
Indicates a relationship where an entity plays an active role in originating, designing, or shaping the creative content or form of another entity.
-
E.
coAuthorOccupation
Indicates that two or more co-authors share the same or closely related professional occupation.
- 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_69f07cb528fc8190a556b73990c347c8 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f662d140a48190ac5910abdba5a91c |
completed | May 2, 2026, 8:47 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65fb2ead08190b06677d4d6ea1ea8 |
completed | May 2, 2026, 8:33 p.m. |
Created at: April 28, 2026, 11:47 a.m.