Triple
T11649047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bristol Cathedral choir |
E276851
|
entity |
| Predicate | usesAccompaniment |
P86608
|
FINISHED |
| Object | organ |
—
|
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: organ | Statement: [Bristol Cathedral choir, usesAccompaniment, organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAccompaniment Context triple: [Bristol Cathedral choir, usesAccompaniment, organ]
-
A.
accompanimentType
Indicates the specific manner or style in which one entity accompanies or supports another (e.g., musically, contextually, or functionally).
-
B.
usuallyAccompaniedBy
Indicates that one entity is commonly or habitually found together with, or occurs in the presence of, another entity.
-
C.
mayBeAccompaniedBy
chosen
Indicates that one entity can optionally be present together with or alongside another entity.
-
D.
traditionalAccompaniment
Indicates that one entity is customarily or culturally served, used, or presented together with another as its traditional accompaniment.
-
E.
accompanimentRole
Indicates the role or function an accompanying entity plays in relation to a primary entity or event.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cd9bb0819093d107204bed2fe0 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.