Triple
T23747705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Risør Chamber Music Festival |
E586862
|
entity |
| Predicate | drawsPerformersFrom |
P56504
|
FINISHED |
| Object | Norway |
—
|
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: Norway | Statement: [Risør Chamber Music Festival, drawsPerformersFrom, Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drawsPerformersFrom Context triple: [Risør Chamber Music Festival, drawsPerformersFrom, Norway]
-
A.
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.
-
B.
numberOfPerformers
Indicates the quantity of performers involved in a given event, act, or performance.
-
C.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
D.
performingMusicians
Indicates that certain musicians are actively giving a performance, typically in association with a specific event, work, or venue.
-
E.
samplePerformer
Indicates that an entity performs, executes, or is responsible for producing a given sample (such as a data sample, test sample, or media sample).
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc058a88190b9addcbf3f063885 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:12 p.m.