Triple
T34693556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greendale |
E890962
|
entity |
| Predicate | genreOfStoriesSetIn |
P169851
|
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: [Greendale, genreOfStoriesSetIn, horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfStoriesSetIn Context triple: [Greendale, genreOfStoriesSetIn, horror]
-
A.
genreOfStoryline
Indicates the relationship in which a particular genre characterizes or classifies the storyline of a work.
-
B.
workOfFictionSetting
chosen
Indicates that a work of fiction is set in, or primarily takes place within, a particular location, time, or environment.
-
C.
literaryGenreOfWorkAppearedIn
Indicates the literary genre of the work in which a given entity (such as a text, character, or element) appears.
-
D.
hasGenreInFiction
Indicates that a work of fiction belongs to or is categorized under a specific literary genre.
-
E.
literaryGenreOfWork
Indicates that a work belongs to or is classified under a particular literary 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_69f349db7ab8819086808e833f472871 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 1, 2026, 2:05 a.m.