Triple
T17729832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Changes (Band of Gypsys song) |
E442556
|
entity |
| Predicate | livePerformanceDateRange |
P115910
|
FINISHED |
| Object | 1969–1970 |
—
|
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: 1969–1970 | Statement: [Changes (Band of Gypsys song), livePerformanceDateRange, 1969–1970]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livePerformanceDateRange Context triple: [Changes (Band of Gypsys song), livePerformanceDateRange, 1969–1970]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
C.
musicDate
chosen
Indicates the date on which a piece of music was created, performed, released, or otherwise took place.
-
D.
livePerformanceContext
Indicates that an action or event occurs within the setting of a live performance, such as a concert, play, or other real-time staged presentation.
-
E.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e5ba7c81908f8b06eb6859067f |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.