Triple
T26443627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tear da Club Up ’97 |
E665151
|
entity |
| Predicate | hasMusicalKeyCharacteristic |
P44121
|
FINISHED |
| Object | aggressive style |
—
|
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: aggressive style | Statement: [Tear da Club Up ’97, hasMusicalKeyCharacteristic, aggressive style]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicalKeyCharacteristic Context triple: [Tear da Club Up ’97, hasMusicalKeyCharacteristic, aggressive style]
-
A.
hasMusicCharacteristic
chosen
Indicates that an entity possesses a specific musical feature, quality, or attribute.
-
B.
musicKey
Indicates the musical key in which a piece of music, passage, or section is composed or performed.
-
C.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
D.
hasMusicalSettingsBy
Indicates that a work has been set to music or musically arranged by a specified creator or composer.
-
E.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining 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_69ee883c851881909e2ab04efbb3c5fe |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, midnight