Triple
T10023936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jerusalem International Chamber Music Festival |
E200678
|
entity |
| Predicate | typicalPerformanceType |
P63774
|
FINISHED |
| Object | chamber music concert |
—
|
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: chamber music concert | Statement: [Jerusalem International Chamber Music Festival, typicalPerformanceType, chamber music concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPerformanceType Context triple: [Jerusalem International Chamber Music Festival, typicalPerformanceType, chamber music concert]
-
A.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
B.
typicalPerformanceMode
Indicates the usual or most common way in which an entity performs an action or operates.
-
C.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
-
D.
typicalPerformerRoleType
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
E.
typeOfPerformances
chosen
Indicates the kinds or categories of performances associated with or offered by an entity.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7c75548190aa604d90d63dc111 |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:53 p.m.