Triple
T29529785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonio |
E749165
|
entity |
| Predicate | musicalCharacterization |
P46763
|
FINISHED |
| Object | heroic and lyrical |
—
|
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: heroic and lyrical | Statement: [Tonio, musicalCharacterization, heroic and lyrical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicalCharacterization Context triple: [Tonio, musicalCharacterization, heroic and lyrical]
-
A.
musicalCharacter
Indicates that one entity is a character or role that appears within the other entity, which is a musical work or production.
-
B.
lyricCharacterization
Indicates how the lyrics portray, describe, or characterize a subject within a song or musical work.
-
C.
musicalAttribute
chosen
Indicates a relationship where a musical work, performance, or element is characterized by a specific musical property or quality (such as tempo, key, style, or mood).
-
D.
hasMusicalStyleCharacteristic
Indicates that something possesses or exhibits a particular musical style as a defining characteristic.
-
E.
musicalDepictionOf
Indicates that one entity is a musical work that artistically represents, portrays, or is inspired by 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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 4:51 p.m.