Triple
T9372672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rock Show |
E225568
|
entity |
| Predicate | precedesInMedley |
P67544
|
FINISHED |
| Object | Jet (live setlists) |
—
|
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: Jet (live setlists) | Statement: [Rock Show, precedesInMedley, Jet (live setlists)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesInMedley Context triple: [Rock Show, precedesInMedley, Jet (live setlists)]
-
A.
precedesInSoundtrack
Indicates that one soundtrack item occurs earlier in the playback order than another within the same soundtrack sequence.
-
B.
precedesTrackOnAlbum
Indicates that one track appears immediately before another track in the ordering of tracks on the same album.
-
C.
precedesSingleInDiscography
Indicates that one musical single was released earlier than another within the same artist’s discography.
-
D.
isMedleyWith
chosen
Indicates that two or more musical pieces are combined and performed together as a continuous medley.
-
E.
precedesSingleArtist
Indicates that one entity occurs or is positioned immediately before a single artist in a sequence, order, or timeline.
- 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_69ca842cbddc819099d71ecec48cf9e5 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50852a388190be936df1382216bc |
completed | April 1, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69cc7a6abb8c81908c7a2f4ee92cc949 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:43 p.m.