Triple
T23614391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BRIT Award for Best British Rock Act (with Kaiser Chiefs) |
E583135
|
entity |
| Predicate | bandOfRecipient |
P52361
|
FINISHED |
| Object | Kaiser Chiefs |
—
|
NE NERFINISHED |
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: Kaiser Chiefs | Statement: [BRIT Award for Best British Rock Act (with Kaiser Chiefs), bandOfRecipient, Kaiser Chiefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bandOfRecipient Context triple: [BRIT Award for Best British Rock Act (with Kaiser Chiefs), bandOfRecipient, Kaiser Chiefs]
-
A.
formedBandIn
Indicates the place or context in which a musical band was originally created or came together.
-
B.
recipientSport
Indicates that one entity is the sport associated with, received by, or designated for another entity.
-
C.
hasBandNumber
Indicates that an entity is associated with a specific band identification number.
-
D.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
E.
associatedBandOfMembers
Indicates a relationship where a specific band is linked to the individual members who belong to or perform in that band.
- 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_69e248fbcd9081908ba08913f9d30826 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b0f71a2481909c3d0d8d0d58e20f |
completed | April 29, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:45 p.m.