Triple
T16715256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Killer |
E406207
|
entity |
| Predicate | bearerGenre |
P124345
|
FINISHED |
| Object | rock and roll |
—
|
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: rock and roll | Statement: [The Killer, bearerGenre, rock and roll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bearerGenre Context triple: [The Killer, bearerGenre, rock and roll]
-
A.
usedGenre
Indicates that one entity employs or is associated with a particular genre in its creation, presentation, or classification.
-
B.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
C.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
D.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
E.
commonGenre
Indicates that two entities share at least one genre in common.
- F. None of above. chosen
Provenance (4 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38654ee4c8190abf36c29d6610a96 |
completed | April 18, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.