Triple
T32727878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I’da Called You Woody, Joe |
E836859
|
entity |
| Predicate | homageToBand |
P25510
|
FINISHED |
| Object | The Clash |
—
|
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: The Clash | Statement: [I’da Called You Woody, Joe, homageToBand, The Clash]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homageToBand Context triple: [I’da Called You Woody, Joe, homageToBand, The Clash]
-
A.
paysHomageTo
Indicates that one entity formally shows respect, reverence, or honor toward another, often acknowledging its superiority, influence, or authority.
-
B.
inspiredByBand
chosen
Indicates that one entity (such as a work, style, or artist) was creatively influenced or motivated by a particular band.
-
C.
homageToComposer
Indicates that one entity pays tribute or respect to a composer, often by referencing, honoring, or being inspired by their work.
-
D.
favoriteBand
Indicates that one entity is the band that another entity likes the most among all bands.
-
E.
hasBand
Indicates that an entity is associated with or includes a particular band (e.g., musical group or band-like unit).
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b953348190bc38ddc49fdd7571 |
completed | May 3, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.