Triple
T20200926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Here |
E493214
|
entity |
| Predicate | notableVocalStyle |
P108283
|
FINISHED |
| Object | emotional 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: emotional vocals | Statement: [Get Here, notableVocalStyle, emotional vocals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVocalStyle Context triple: [Get Here, notableVocalStyle, emotional vocals]
-
A.
artisticVocalStyle
chosen
Indicates a relationship where an entity’s vocal performance is characterized by a particular artistic style or expressive manner of singing or speaking.
-
B.
hasNotableVocalType
Indicates that an entity is associated with a specific, noteworthy type or quality of vocalization or voice.
-
C.
hasVocalStyleComparedTo
Indicates a comparison between entities based on the similarity or resemblance of their vocal style.
-
D.
hasMusicalVocalType
Indicates that an entity is associated with a specific type or classification of singing voice.
-
E.
vocalPerformanceNotedFor
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
- 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d8d01648190b1b3a6e03f0258d8 |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:37 p.m.