Triple
T14611763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claude McKnight |
E342977
|
entity |
| Predicate | voiceTypeInGroup |
P104659
|
FINISHED |
| Object | lead tenor |
—
|
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: lead tenor | Statement: [Claude McKnight, voiceTypeInGroup, lead tenor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voiceTypeInGroup Context triple: [Claude McKnight, voiceTypeInGroup, lead tenor]
-
A.
voiceType
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
vocalGroupPosition
chosen
Indicates the role or placement an entity holds within a vocal group, such as their part, rank, or position in the ensemble.
-
C.
vocalHarmonyType
Indicates the specific kind or style of vocal harmony relationship that exists between the involved vocal parts or voices.
-
D.
typicalNumberOfVoices
Indicates the usual or characteristic number of distinct voices or parts involved in performing or realizing something (such as a musical work or texture).
-
E.
hasVoiceIn
Indicates that an entity participates by providing a voice role or vocal performance in another entity, such as a work, production, or recording.
- 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb450e6588190a94488d8e71888c8 |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.