Triple
T23260909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Get Em |
E582002
|
entity |
| Predicate | vocalPerformanceCharacteristic |
P33230
|
FINISHED |
| Object | high-energy |
—
|
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: high-energy | Statement: [Get Em, vocalPerformanceCharacteristic, high-energy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vocalPerformanceCharacteristic Context triple: [Get Em, vocalPerformanceCharacteristic, high-energy]
-
A.
vocalizationCharacteristic
Indicates how an entity’s vocal sounds are characterized, such as their quality, style, or distinctive acoustic features.
-
B.
featuresVocal
Indicates that one entity includes or presents the vocal performance or voice of another entity.
-
C.
vocalPerformanceNotedFor
chosen
Indicates that a particular vocal performance is recognized or distinguished for a specific quality, feature, or characteristic.
-
D.
vocalPerformanceReception
Indicates how a vocal performance is received, evaluated, or responded to by an audience, critics, or listeners.
-
E.
hasVocalPerformanceBy
Indicates that a vocal performance in a work or recording is performed by a specified person or group.
- 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_69e246079f58819085eaa9c260906880 |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f194c9189c8190a13c17c635227f42 |
completed | April 29, 2026, 5:19 a.m. |
| PD | Predicate disambiguation | batch_69effce4d704819092826931d430e8c4 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:11 p.m.