Triple
T20315598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Festival Republic Stage |
E510370
|
entity |
| Predicate | targetPerformers |
P56504
|
FINISHED |
| Object | emerging UK artists |
—
|
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 UK artists | Statement: [Festival Republic Stage, targetPerformers, emerging UK artists]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetPerformers Context triple: [Festival Republic Stage, targetPerformers, emerging UK artists]
-
A.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
B.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
C.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
-
D.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
E.
bringsPerformersFrom
chosen
Indicates a relationship where one entity arranges for or causes performers to come from a particular source, place, or group to another context or location.
- 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.