Triple
T29652978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At the Bottom of Everything |
E750188
|
entity |
| Predicate | hasGroupVocals |
P83531
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [At the Bottom of Everything, hasGroupVocals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupVocals Context triple: [At the Bottom of Everything, hasGroupVocals, true]
-
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.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
C.
hasNoLeadVocals
Indicates that the referenced musical work or track does not feature any lead vocal performance.
-
D.
hasCallAndResponseVocals
Indicates that one entity produces vocalizations that are followed by corresponding or answering vocalizations from another entity.
-
E.
containsVocalHarmonies
chosen
Indicates that the subject includes multiple vocal parts sung together in harmony.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 28, 2026, 6:53 p.m.