Triple
T28760041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consolação |
E731783
|
entity |
| Predicate | isInstrumentalOrVocal |
P46729
|
FINISHED |
| Object | both (depending on arrangement) |
—
|
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: both (depending on arrangement) | Statement: [Consolação, isInstrumentalOrVocal, both (depending on arrangement)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInstrumentalOrVocal Context triple: [Consolação, isInstrumentalOrVocal, both (depending on arrangement)]
-
A.
isNonVocalInstrumental
Indicates that an entity produces instrumental sound without involving vocalization.
-
B.
isInstrumental
chosen
Indicates that one entity serves as the means, tool, or instrument by which another entity performs an action or achieves an outcome.
-
C.
isNonInstrumental
Indicates that the relationship or action occurs without using an instrument, tool, or intermediary means.
-
D.
usesVocalInstrument
Indicates that an entity performs or produces sound using their voice as a musical instrument.
-
E.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
- 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_69f043ed68a881909e858a06bab7a247 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:11 a.m.