Triple
T34842013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Melton |
E1004366
|
entity |
| Predicate | vocalPerformanceRole |
P24740
|
FINISHED |
| Object | tenor soloist |
—
|
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: tenor soloist | Statement: [James Melton, vocalPerformanceRole, tenor soloist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformanceRole Context triple: [James Melton, vocalPerformanceRole, tenor soloist]
-
A.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
B.
providedVocalPerformanceFor
Indicates that one entity delivered or contributed a vocal performance in support of, or as part of, another entity’s work, event, or production.
-
C.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
D.
musicalRole
chosen
Indicates the specific function or part an entity performs within a musical context, such as in a performance, composition, or ensemble.
-
E.
vocalCounterpartType
Indicates the type or category of a vocal counterpart relationship that one entity has to another (e.g., spoken, sung, dubbed, narrated).
- 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_69f76db97714819099b5bed36fd64e9d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4 p.m.