Triple
T20315614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC Introducing Stage |
E510371
|
entity |
| Predicate | typicalPerformerType |
P14195
|
FINISHED |
| Object | emerging bands |
—
|
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: emerging bands | Statement: [BBC Introducing Stage, typicalPerformerType, emerging bands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformerType Context triple: [BBC Introducing Stage, typicalPerformerType, emerging bands]
-
A.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
B.
performerType
Indicates the role or category of performer responsible for carrying out an action or participating in an event.
-
C.
typicalPerformers
chosen
Indicates the entities that most commonly or characteristically perform a given action or role.
-
D.
typicalPerformerCount
Indicates the usual or standard number of performers involved in carrying out the associated activity or event.
-
E.
traditionalPerformer
Indicates that an entity performs or practices traditional, culturally inherited arts, rituals, or performances.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67786f4dc8190b02a6c2a4338362d |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.