Triple
T860070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Church choir |
E18578
|
entity |
| Predicate | musicFocus |
P20265
|
FINISHED |
| Object | English sacred music |
—
|
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: English sacred music | Statement: [Temple Church choir, musicFocus, English sacred music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicFocus Context triple: [Temple Church choir, musicFocus, English sacred music]
-
A.
musicBy
Indicates that a piece of music, performance, or recording is created, composed, or performed by a specified musical artist or group.
-
B.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
C.
musicFusionOf
Indicates a relationship where one musical work, style, or element is created by combining or blending two or more distinct musical sources or genres.
-
D.
musicMovement
Indicates a relationship where a musical work, performance, or composition is associated with a specific movement or section within a larger musical piece.
-
E.
musicDriven
Indicates that one entity’s behavior, structure, or progression is guided, influenced, or determined primarily by music or musical elements.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac52536c8190ab198232e9ec4bd6 |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa84835081908aaf98b10656d7d6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.