Triple
T30569156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mummy (1932 film) |
E778072
|
entity |
| Predicate | costumeMakeupBy |
P113105
|
FINISHED |
| Object | Jack Pierce |
—
|
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: Jack Pierce | Statement: [The Mummy (1932 film), costumeMakeupBy, Jack Pierce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeMakeupBy Context triple: [The Mummy (1932 film), costumeMakeupBy, Jack Pierce]
-
A.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
B.
makeupArtist
Indicates that one entity serves as the makeup artist for another, applying or designing cosmetic looks for that entity.
-
C.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
D.
usesStageMakeup
Indicates that one entity applies or wears theatrical or stage makeup in relation to another entity or context.
-
E.
hasMakeupEffectsBy
chosen
Indicates that the makeup effects for an entity (such as a film or production) are created or supervised by a specified person or team.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68911752c8190bc42c92fce473f3c |
completed | May 2, 2026, 11:30 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:21 p.m.