Triple
T21872758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siberian Khatru |
E540048
|
entity |
| Predicate | isConcertStapleOf |
P3288
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Siberian Khatru, isConcertStapleOf, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isConcertStapleOf Context triple: [Siberian Khatru, isConcertStapleOf, Yes]
-
A.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
-
B.
isConcertOpener
Indicates that one performer, act, or event serves as the opening performance for another concert or main act.
-
C.
isClassicRockStaple
Indicates that something is a well-known, frequently played, and culturally significant song or piece within the classic rock genre.
-
D.
livePerformanceStapleFor
chosen
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
E.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f337ab5c8190937a457d348c732b |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 7 p.m.