Triple
T35162967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot (American Horror Story) |
E1015318
|
entity |
| Predicate | introducesCharacterGroup |
P196339
|
FINISHED |
| Object | Harmon family |
—
|
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: Harmon family | Statement: [Pilot (American Horror Story), introducesCharacterGroup, Harmon family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesCharacterGroup Context triple: [Pilot (American Horror Story), introducesCharacterGroup, Harmon family]
-
A.
titleCharacterGroup
Indicates that a group of characters is associated with or featured in the title of a work.
-
B.
hasCharacterGroupName
Indicates that an entity is associated with a specific name identifying a group of characters.
-
C.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
D.
settingForCharacterGroup
Indicates the contextual environment or location in which a particular group of characters collectively exists, acts, or is situated.
-
E.
groupCharacterization
Indicates how a group as a whole is described or characterized in terms of its shared properties, traits, or defining features.
- F. None of above. chosen
Provenance (4 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_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
| PDg | Predicate description generation | batch_69fe21afdc4c8190913ac4b55a9a5f52 |
completed | May 8, 2026, 5:47 p.m. |
Created at: May 3, 2026, 4:02 p.m.