Triple
T3286043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jacinto |
E68983
|
entity |
| Predicate | hasGenreContext |
P20075
|
FINISHED |
| Object | supernatural 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: supernatural horror | Statement: [Jacinto, hasGenreContext, supernatural horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenreContext Context triple: [Jacinto, hasGenreContext, supernatural horror]
-
A.
hasGenreScope
Indicates that something (such as a work, collection, or classification) is limited to, defined by, or applicable within a particular genre or set of genres.
-
B.
hasGenreList
Indicates that an entity is associated with a set or list of genres that categorize or describe it.
-
C.
hasGenreInfluenceOn
Indicates that one genre has a notable impact on shaping or influencing the characteristics, style, or development of another genre.
-
D.
hasGenreArtist
Indicates that an artist is associated with or specializes in a particular genre.
-
E.
genreContext
chosen
Indicates the contextual genre or categorical style associated with an entity, such as the thematic or stylistic framework in which it is situated.
- 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_69ad859c463481909ca4be267336c290 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb03918c48190987d7cfd3bda9716 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.