Triple
T18357087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Word |
E439822
|
entity |
| Predicate | hasProminentHarmonyVocals |
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: [The Word, hasProminentHarmonyVocals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProminentHarmonyVocals Context triple: [The Word, hasProminentHarmonyVocals, true]
-
A.
containsVocalHarmonies
chosen
Indicates that the subject includes multiple vocal parts sung together in harmony.
-
B.
hasVocals
Indicates that the subject includes or features vocal elements, such as singing or spoken voice, rather than being purely instrumental or non-vocal.
-
C.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
D.
hasEnergeticVocals
Indicates that the subject performs vocals characterized by high energy, intensity, or liveliness.
-
E.
hasCallAndResponseVocals
Indicates that one entity produces vocalizations that are followed by corresponding or answering vocalizations from another entity.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516d776cc8190937d7e1d42a36a3b |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.