Triple
T379653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curly McLain |
E8649
|
entity |
| Predicate | hasStageVoiceType |
P2000
|
FINISHED |
| Object | baritone |
—
|
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: baritone | Statement: [Curly McLain, hasStageVoiceType, baritone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStageVoiceType Context triple: [Curly McLain, hasStageVoiceType, baritone]
-
A.
voiceType
chosen
Indicates the specific vocal style, quality, or role associated with an entity’s voice in a given context.
-
B.
vocalizationMethod
Indicates the manner or technique by which an entity produces a sound or vocal expression.
-
C.
vocalRange
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
-
D.
hasStageType
Indicates that an entity is associated with, or classified by, a specific type or category of stage within a process, lifecycle, or workflow.
-
E.
hasPhonologicalType
Indicates that one entity is characterized by or classified as having a particular phonological type (e.g., in terms of sound structure or phonological category).
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2b07248190979229bad3a741c9 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e964d4b481909290e474b0341e3c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.