Triple
T29732114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henry |
E752354
|
entity |
| Predicate | hasCultStatusContext |
P180596
|
FINISHED |
| Object | cult horror film icon |
—
|
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: cult horror film icon | Statement: [Henry, hasCultStatusContext, cult horror film icon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCultStatusContext Context triple: [Henry, hasCultStatusContext, cult horror film icon]
-
A.
hasCultSince
Indicates that an entity has had an organized group of devoted followers (a cult) continuously since a specified time or date.
-
B.
hasSubcultureStatus
chosen
Indicates that an entity holds a particular role, recognition, or standing within a specific subculture or subcultural context.
-
C.
hasAttestedCult
Indicates that an entity is known to have had an established, historically attested cult or formal worship practice.
-
D.
hasCultFilmStatus
Indicates that a film has achieved cult status, typically through a dedicated, passionate fanbase despite limited or non-mainstream popularity.
-
E.
hasCultFeature
Indicates that an entity possesses a characteristic, attribute, or element associated with cultic or ritual practices.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 28, 2026, 7:43 p.m.