Triple
T28675206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Shining (film score) |
E725843
|
entity |
| Predicate | originallyComposedForGenre |
P181060
|
FINISHED |
| Object | horror film |
—
|
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 film | Statement: [The Shining (film score), originallyComposedForGenre, horror film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyComposedForGenre Context triple: [The Shining (film score), originallyComposedForGenre, horror film]
-
A.
hasGenreOfOrigin
Indicates that an entity’s original or primary genre classification is the specified genre.
-
B.
primarySourceGenre
Indicates the genre or type of creative work that serves as the primary source for something (e.g., an adaptation, derivative work, or related resource).
-
C.
musicOriginallyComposedFor
chosen
Indicates that a piece of music was initially created specifically for a particular work, medium, or context.
-
D.
hasGenreOrigin
Indicates that a genre originates from, or has its roots in, a particular source, place, culture, or tradition.
-
E.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 28, 2026, 5:06 a.m.