Triple
T30466656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letter to You Tour |
E775159
|
entity |
| Predicate | hasTribute |
P197165
|
FINISHED |
| Object | Clarence Clemons |
—
|
NE NERFINISHED |
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: Clarence Clemons | Statement: [Letter to You Tour, hasTribute, Clarence Clemons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribute Context triple: [Letter to You Tour, hasTribute, Clarence Clemons]
-
A.
typeOfTribute
Indicates the specific kind or category of tribute that is being given or required in a relationship.
-
B.
requiredTributeTo
Indicates that one entity is obligated to provide a tribute or payment to another entity.
-
C.
hasTributeReleasesFor
Indicates that one entity has released or produced tribute works (such as albums, songs, or performances) dedicated to another entity.
-
D.
hasFanTributeUse
Indicates that something is used, referenced, or incorporated within a fan-created tribute to a work, person, or entity.
-
E.
subjectOfTribute
Indicates that one entity is the target or honoree of a tribute, such as a payment, offering, or act of respect made by another entity.
- F. None of above. chosen
Provenance (4 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe7b1c506c8190869c1a22031e0571 |
completed | May 9, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69fe796b2bdc8190a86980d44008f875 |
completed | May 9, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69fe7b1b3460819081172731b52ac15b |
completed | May 9, 2026, 12:08 a.m. |
Created at: April 29, 2026, 8:11 p.m.