Triple
T14860544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love Divine, All Loves Excelling |
E349474
|
entity |
| Predicate | commonlySungIn |
P32287
|
FINISHED |
| Object | Methodist 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: Methodist churches | Statement: [Love Divine, All Loves Excelling, commonlySungIn, Methodist churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlySungIn Context triple: [Love Divine, All Loves Excelling, commonlySungIn, Methodist churches]
-
A.
frequentlySings
Indicates that the subject engages in the act of singing on a regular or repeated basis.
-
B.
isTraditionallySungBy
chosen
Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
-
C.
commonlySungStanzas
Indicates that certain stanzas of a song or poem are those most frequently sung or performed in practice.
-
D.
sangSongsIn
Indicates that one entity performed or vocalized songs in the context, location, or event associated with another entity.
-
E.
singsTo
Indicates that one entity performs singing directed toward or for another entity.
- 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.