Triple
T27176274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Responsorial Psalm |
E683050
|
entity |
| Predicate | musicalSettingMayBe |
P169933
|
FINISHED |
| Object | simple chant |
—
|
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: simple chant | Statement: [Responsorial Psalm, musicalSettingMayBe, simple chant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalSettingMayBe Context triple: [Responsorial Psalm, musicalSettingMayBe, simple chant]
-
A.
settingInMusical
Indicates that one entity serves as the setting or location in which the events of a musical take place.
-
B.
notableMusicalSetting
Indicates that a work or text has been set to music in a particularly significant, recognized, or influential way.
-
C.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
D.
musicalScene
Indicates a relationship where a scene in a work prominently features musical performance or music-driven action.
-
E.
theatricalSetting
Indicates the spatial or contextual environment in which a theatrical performance or dramatic action takes place.
- 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_69eefad086808190ab89816c0c300476 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f688d015908190ad5df37030ecf332 |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 27, 2026, 9:26 a.m.