Triple
T30103979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Movin' Blues |
E765078
|
entity |
| Predicate | includedInLiveSet |
P202110
|
FINISHED |
| Object | One World Concert tour repertoire |
—
|
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: One World Concert tour repertoire | Statement: [Movin' Blues, includedInLiveSet, One World Concert tour repertoire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedInLiveSet Context triple: [Movin' Blues, includedInLiveSet, One World Concert tour repertoire]
-
A.
isOnLiveAlbum
Indicates that an item (such as a song or performance) appears on a live album recording rather than a studio or other type of release.
-
B.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
C.
isPartOfEnsemble
Indicates that an entity belongs to, or is a member of, a larger group or ensemble.
-
D.
hasLivePerformanceSetting
Indicates that an entity is associated with a particular context or environment in which a live performance takes place.
-
E.
includedInStandardRepertoire
Indicates that something is part of the commonly accepted or regularly used set within a particular standard repertoire.
- F. None of above. chosen
Provenance (4 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
| PDg | Predicate description generation | batch_6a00524723408190b0294e87e5cf7715 |
completed | May 10, 2026, 9:39 a.m. |
Created at: April 29, 2026, 7:09 p.m.