Triple
T18879446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snowfort Pictures |
E461784
|
entity |
| Predicate | workIncludesGenre |
P14417
|
FINISHED |
| Object | horror |
—
|
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: horror | Statement: [Snowfort Pictures, workIncludesGenre, horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workIncludesGenre Context triple: [Snowfort Pictures, workIncludesGenre, horror]
-
A.
belongsToWorkGenre
Indicates that a creative work is classified under or associated with a particular genre.
-
B.
workedOnGenre
chosen
Indicates that an entity (such as a person or organization) has done work related to a particular genre.
-
C.
hasGenreInRoles
Indicates that an entity participates in roles associated with a particular genre or set of genres.
-
D.
hasGenreInPortfolio
Indicates that an entity (such as a creator, label, or catalog) includes a particular genre within its body of work or offerings.
-
E.
includedInGenreCollection
Indicates that something is a member of, or contained within, a specific genre-based 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_69d8dcfc3430819095ee6fc0eb4c06a5 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c3d06ef481908bba297d7a1fd011 |
completed | April 20, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69e48d22dde8819093b1d963bd673365 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:57 a.m.