Triple
T22520167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geistliche Chormusik |
E556751
|
entity |
| Predicate | intendedPerformers |
P116845
|
FINISHED |
| Object | professional church choirs |
—
|
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: professional church choirs | Statement: [Geistliche Chormusik, intendedPerformers, professional church choirs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPerformers Context triple: [Geistliche Chormusik, intendedPerformers, professional church choirs]
-
A.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
B.
intendedForPerformanceBy
chosen
Indicates that something (such as a work, role, or piece) is designed or meant to be performed by a particular performer or type of performer.
-
C.
numberOfPerformers
Indicates the quantity of performers involved in a given event, act, or performance.
-
D.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
E.
numberOfMainPerformers
Indicates the count of primary performers involved in a performance or event.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e31f43c8190899f5e35b150fe85 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.