Triple
T20178154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night of the Living Dummy |
E492652
|
entity |
| Predicate | hasTaglineType |
P87388
|
FINISHED |
| Object | Goosebumps-style horror tagline on cover |
—
|
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: Goosebumps-style horror tagline on cover | Statement: [Night of the Living Dummy, hasTaglineType, Goosebumps-style horror tagline on cover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTaglineType Context triple: [Night of the Living Dummy, hasTaglineType, Goosebumps-style horror tagline on cover]
-
A.
hasTagline
Indicates that an entity is associated with a specific slogan or tagline that represents or promotes it.
-
B.
hasSloganType
chosen
Indicates the specific category or type of slogan associated with an entity.
-
C.
taglineForm
Indicates that one entity serves as the tagline or slogan associated with another entity.
-
D.
taglineMatch
Indicates that two entities share the same tagline or that a tagline corresponds to a given entity.
-
E.
hasSloganOrKeyPhrase
Indicates that an entity is associated with a specific slogan, tagline, or key phrase used to represent or promote it.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668ed07c8819091bd9ffda237a91c |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.