Triple
T32469057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Crow (film score) |
E829794
|
entity |
| Predicate | followsToneOf |
P49759
|
FINISHED |
| Object | gothic superhero film tone |
—
|
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: gothic superhero film tone | Statement: [The Crow (film score), followsToneOf, gothic superhero film tone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsToneOf Context triple: [The Crow (film score), followsToneOf, gothic superhero film tone]
-
A.
contributesToTone
chosen
Indicates that one entity plays a role in shaping, influencing, or determining the overall tone or mood of another entity.
-
B.
followsSoundOf
Indicates that one entity moves or directs its attention by tracking the source or direction of a sound produced by another entity.
-
C.
haveTone
Indicates that an entity possesses or exhibits a particular tone, such as a specific attitude, mood, or quality of expression.
-
D.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
E.
toneInSeries
Indicates the tonal quality or mood that characterizes a particular work within a series or the series as a whole.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: May 1, 2026, 12:57 a.m.