Triple
T34661726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countach (For Giorgio) |
E890127
|
entity |
| Predicate | hasTributeType |
P102330
|
FINISHED |
| Object | musical tribute |
—
|
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: musical tribute | Statement: [Countach (For Giorgio), hasTributeType, musical tribute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTributeType Context triple: [Countach (For Giorgio), hasTributeType, musical tribute]
-
A.
hasTribute
Indicates that one entity pays or owes tribute to another entity, typically as a sign of submission, allegiance, or obligation.
-
B.
typeOfTribute
chosen
Indicates the specific kind or category of tribute that is being given or required in a relationship.
-
C.
requiredTributeTo
Indicates that one entity is obligated to provide a tribute or payment to another entity.
-
D.
hasTributeReleasesFor
Indicates that one entity has released or produced tribute works (such as albums, songs, or performances) dedicated to another entity.
-
E.
isTributeAlbum
Indicates that one musical album is created as a tribute to another artist, band, or specific work, typically featuring covers or reinterpretations of their songs.
- 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_69f349d906bc8190b2efd9eff237d94b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
Created at: May 1, 2026, 2:04 a.m.