Triple
T34043326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Peter Criss Band |
E873009
|
entity |
| Predicate | playsMaterialFrom |
P180836
|
FINISHED |
| Object | Kiss-related repertoire |
—
|
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: Kiss-related repertoire | Statement: [The Peter Criss Band, playsMaterialFrom, Kiss-related repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsMaterialFrom Context triple: [The Peter Criss Band, playsMaterialFrom, Kiss-related repertoire]
-
A.
playsMaterialBy
chosen
Indicates that an agent performs or executes a piece of material (such as a work, composition, or content) created or provided by another entity.
-
B.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
C.
playSource
Indicates that an entity serves as the origin or provider from which a play or playback action is initiated.
-
D.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
E.
playsWithin
Indicates that one entity performs or takes place inside the spatial or temporal bounds of another entity.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:51 a.m.