Triple
T21051749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worcester Cathedral Choir |
E518602
|
entity |
| Predicate | regularlyPerforms |
P62471
|
FINISHED |
| Object | daily services |
—
|
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: daily services | Statement: [Worcester Cathedral Choir, regularlyPerforms, daily services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regularlyPerforms Context triple: [Worcester Cathedral Choir, regularlyPerforms, daily services]
-
A.
isFrequentlyPerformedBy
chosen
Indicates that an action or activity is carried out often or on a regular basis by a particular entity.
-
B.
frequentlyPerformedAt
Indicates that an action or event occurs regularly or with high frequency at a particular location or context.
-
C.
meetsRegularly
Indicates that two or more entities come together on a recurring or scheduled basis.
-
D.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
E.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
- 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_69e0b5053ac48190921529544959e906 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fd7bd96c81909cb46419ad4e1222 |
completed | April 21, 2026, 4:30 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 2:35 p.m.