Triple
T29664708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Show Me the Way |
E750496
|
entity |
| Predicate | includedInLiveSetlistsOf |
P33226
|
FINISHED |
| Object | Peter Frampton |
—
|
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: Peter Frampton | Statement: [Show Me the Way, includedInLiveSetlistsOf, Peter Frampton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInLiveSetlistsOf Context triple: [Show Me the Way, includedInLiveSetlistsOf, Peter Frampton]
-
A.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
B.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
C.
typicalSetlistStatus
Indicates the usual or expected status of an item within a standard or commonly performed setlist.
-
D.
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.
-
E.
performedInConcertBy
Indicates that an action, piece, or performance was carried out jointly by multiple participants as part of the same concert event.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
Created at: April 28, 2026, 7 p.m.