Triple
T9042544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Nightwatchman |
E216667
|
entity |
| Predicate | hasTypeOfVocals |
P46281
|
FINISHED |
| Object | baritone vocals |
—
|
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 vocals | Statement: [The Nightwatchman, hasTypeOfVocals, baritone vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfVocals Context triple: [The Nightwatchman, hasTypeOfVocals, baritone vocals]
-
A.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
B.
hasNotableVocalType
chosen
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
C.
hasCallAndResponseVocals
Indicates that one entity produces vocalizations that are followed by corresponding or answering vocalizations from another entity.
-
D.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
-
E.
containsVocalSamplesFrom
Indicates that one audio work includes vocal samples that originate from another audio work.
- 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_69ca83d22d488190adbce5e020e9cd1d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b1228748190be0c4afe6e0bd9a3 |
completed | April 1, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:09 p.m.