Triple
T6787686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Choir of Trinity College, Cambridge |
E155851
|
entity |
| Predicate | voiceParts |
P2000
|
FINISHED |
| Object | soprano |
—
|
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: soprano | Statement: [Choir of Trinity College, Cambridge, voiceParts, soprano]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceParts Context triple: [Choir of Trinity College, Cambridge, voiceParts, soprano]
-
A.
voiceWork
Indicates that one entity performs or contributes voice acting or vocal performance work for another entity or creative production.
-
B.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
C.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
-
D.
speechType
Indicates the specific category or form of spoken or written communication that an utterance or speech act belongs to (e.g., question, statement, command).
-
E.
speakerFeatures
Indicates that certain characteristics, attributes, or properties are associated with a speaker in a given context.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d2907d0081908291aad66048b8b1 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.