Triple
T14860669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christ the Lord Is Risen Today |
E349477
|
entity |
| Predicate | isSungIn |
P112229
|
FINISHED |
| Object | churches |
—
|
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: churches | Statement: [Christ the Lord Is Risen Today, isSungIn, churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSungIn Context triple: [Christ the Lord Is Risen Today, isSungIn, churches]
-
A.
isSungBy
Indicates that a song, piece of music, or vocal performance is performed vocally by a particular singer or group of singers.
-
B.
sungIn
Indicates that something (such as a song, lyric, or performance) is performed vocally using a particular language, style, or vocal context.
-
C.
sungAs
Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
-
D.
sangSongsIn
chosen
Indicates that one entity performed or vocalized songs in the context, location, or event associated with another entity.
-
E.
isSignatureSongOf
Indicates that a particular song is widely recognized as the most iconic or defining song associated with a specific artist or group.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:54 a.m.