Triple
T11020531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sofia (Climax) |
E260474
|
entity |
| Predicate | appearsInGenreContext |
P21332
|
FINISHED |
| Object | hallucinatory horror drama |
—
|
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: hallucinatory horror drama | Statement: [Sofia (Climax), appearsInGenreContext, hallucinatory horror drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInGenreContext Context triple: [Sofia (Climax), appearsInGenreContext, hallucinatory horror drama]
-
A.
genreOfAppearance
chosen
Indicates the genre or type of creative work in which an entity appears.
-
B.
coveredInGenre
Indicates that a work or item is associated with, categorized under, or treated within a particular genre.
-
C.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
D.
includedInGenreCollection
Indicates that something is a member of, or contained within, a specific genre-based collection.
-
E.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797baad408190a53fd6941a750f68 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.