Triple
T25281603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live at Budokan |
E633837
|
entity |
| Predicate | featuresLiveVersionOf |
P85821
|
FINISHED |
| Object | I Want You to Want Me |
—
|
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: I Want You to Want Me | Statement: [Live at Budokan, featuresLiveVersionOf, I Want You to Want Me]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLiveVersionOf Context triple: [Live at Budokan, featuresLiveVersionOf, I Want You to Want Me]
-
A.
featuresReimaginedVersionOf
Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
-
B.
liveVersionType
Indicates the type or category of a version that is currently live or active.
-
C.
liveVersionTitle
Indicates the title associated with the live or currently active version of something (such as a document, release, or piece of content).
-
D.
notableLiveVersion
chosen
Indicates that one work is a particularly significant or well-known live performance version of another work.
-
E.
featureOfReleases
Indicates that certain features are associated with, included in, or introduced as part of specific releases.
- 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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a5fd8481909433e923c5e24e55 |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 21, 2026, 1:19 p.m.