Triple
T35162980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot (American Horror Story) |
E1015318
|
entity |
| Predicate | introducesStoryArc |
P163477
|
FINISHED |
| Object | Murder House haunting |
—
|
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: Murder House haunting | Statement: [Pilot (American Horror Story), introducesStoryArc, Murder House haunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesStoryArc Context triple: [Pilot (American Horror Story), introducesStoryArc, Murder House haunting]
-
A.
storyArcStart
chosen
Indicates the point in a narrative where a particular story arc or plotline begins.
-
B.
notableStoryArc
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
firstMajorStoryArc
Indicates that the related entity represents the initial or earliest major story arc associated with another narrative work or series.
-
D.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
E.
firstRegularStory
Indicates that an entity is the earliest or primary standard (non-special) story associated with another entity in a sequence or collection.
- 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_69f76ddbfde081908bffc91572368289 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 3, 2026, 4:02 p.m.