Triple
T20114440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Douglas Pipes |
E490417
|
entity |
| Predicate | notableGenreCombination |
P85590
|
FINISHED |
| Object | horror and comedy |
—
|
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 and comedy | Statement: [Douglas Pipes, notableGenreCombination, horror and comedy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGenreCombination Context triple: [Douglas Pipes, notableGenreCombination, horror and comedy]
-
A.
notableGenreCollaboration
Indicates a collaborative relationship between entities that is particularly significant or well-known within a specific genre.
-
B.
combinesGenre
chosen
Indicates that an entity integrates or merges multiple genres into a single combined form or work.
-
C.
notableWorkGenre
Indicates that a particular work is recognized as notable for an entity and specifies the genre to which that work belongs.
-
D.
hasNotableGenre
Indicates that an entity is significantly associated with a particular genre, such that the genre is especially characteristic or noteworthy for that entity.
-
E.
notableGenreAdaptation
Indicates that a work is a significant adaptation of another work into a different 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e31af081908d8e0c867c388a73 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.