Triple
T1655407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reformed Congregations |
E35786
|
entity |
| Predicate | musicPractice |
P30950
|
FINISHED |
| Object | exclusive or near-exclusive psalm singing |
—
|
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: exclusive or near-exclusive psalm singing | Statement: [Reformed Congregations, musicPractice, exclusive or near-exclusive psalm singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicPractice Context triple: [Reformed Congregations, musicPractice, exclusive or near-exclusive psalm singing]
-
A.
musicElement
Indicates a relationship where something functions as a component or structural unit within a piece of music or musical composition.
-
B.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
C.
musicalAbility
Indicates that an entity possesses skill, talent, or proficiency in performing, creating, or understanding music.
-
D.
musicalMode
Indicates the specific tonal framework or scale system (mode) in which a piece of music or musical passage is organized.
-
E.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
- F. None of above. chosen
Provenance (4 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a99a4c3810819089d2dd0e23c8e46b |
completed | March 5, 2026, 2:59 p.m. |
Created at: March 4, 2026, 7:29 p.m.