Triple
T23481949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | They're Creeping Up on You! |
E570427
|
entity |
| Predicate | positionInAnthology |
P81123
|
FINISHED |
| Object | one of five main segments in Creepshow |
—
|
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: one of five main segments in Creepshow | Statement: [They're Creeping Up on You!, positionInAnthology, one of five main segments in Creepshow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInAnthology Context triple: [They're Creeping Up on You!, positionInAnthology, one of five main segments in Creepshow]
-
A.
numberInAnthology
Indicates the specific position or sequence number that a work occupies within an anthology.
-
B.
positionInAuthorOeuvre
Indicates the relative placement or order of a work within an author's overall body of work.
-
C.
positionInStory
Indicates the point or role an event, character, or element occupies within the overall sequence or structure of a story.
-
D.
isAnthologySegmentOf
chosen
Indicates that one work or segment is a constituent part or episode within a larger anthology work.
-
E.
positionInFiction
Indicates that one entity holds a specific role, status, or placement within a fictional work or narrative.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a75118048190b4af687906c4e747 |
completed | April 29, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:03 p.m.