Triple
T25142015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ely Cathedral Choir |
E629826
|
entity |
| Predicate | notableDirectorOfMusic |
P144231
|
FINISHED |
| Object | Arthur Wills |
—
|
NE NERFINISHED |
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: Arthur Wills | Statement: [Ely Cathedral Choir, notableDirectorOfMusic, Arthur Wills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDirectorOfMusic Context triple: [Ely Cathedral Choir, notableDirectorOfMusic, Arthur Wills]
-
A.
notableConductor
Indicates that the subject is a conductor who is recognized as notable or distinguished in their field.
-
B.
notableMusician
Indicates that the subject is a musician who is widely recognized or distinguished for their musical work or impact.
-
C.
notableDirector
Indicates that a person has directed a work (such as a film or show) in a way that is recognized as significant or distinguished.
-
D.
musicDirectorRole
chosen
Indicates that one entity serves in the role of music director for another entity, such as a production, organization, or event.
-
E.
notableRecordingConductor
Indicates that the object is a conductor who is notably associated with conducting a particular recording of the subject work or performance.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 18, 2026, 6:29 a.m.