Triple
T12997837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harmon family |
E322087
|
entity |
| Predicate | reappearsAs |
P82714
|
FINISHED |
| Object | ghosts in Murder House in later seasons |
—
|
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: ghosts in Murder House in later seasons | Statement: [Harmon family, reappearsAs, ghosts in Murder House in later seasons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reappearsAs Context triple: [Harmon family, reappearsAs, ghosts in Murder House in later seasons]
-
A.
reappearsAt
Indicates that an entity, after having disappeared or been absent, becomes present again at a specific location or point in time.
-
B.
reemergesAs
chosen
Indicates that an entity that previously disappeared, transformed, or became inactive later appears again in a new or altered form.
-
C.
appearsAs
Indicates that one entity is presented, perceived, or manifested in the form, role, or guise of another entity.
-
D.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
E.
laterAppearanceName
Indicates that an entity is known by a different name in a later appearance or time period.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e7980288190a9fe629a8cc76a52 |
completed | April 10, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69d97dc153a081909d13a694993f074a |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:46 p.m.