Triple
T6408536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Joshua Tree 2017 Tour |
E127647
|
entity |
| Predicate | setlistFocus |
P33226
|
FINISHED |
| Object | The Joshua Tree album played in full |
—
|
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: The Joshua Tree album played in full | Statement: [The Joshua Tree 2017 Tour, setlistFocus, The Joshua Tree album played in full]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setlistFocus Context triple: [The Joshua Tree 2017 Tour, setlistFocus, The Joshua Tree album played in full]
-
A.
musicFocus
Indicates that the primary attention or emphasis is directed toward music or musical aspects.
-
B.
setToMusicIn
Indicates that something (typically text or lyrics) has been arranged or adapted to be performed as music within a particular work or context.
-
C.
focusesBy
Indicates that one entity directs its attention, effort, or emphasis toward another entity or specific aspect of it.
-
D.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068ccd804819097b106604372c14a |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f40ecc8190b1df17b96767675c |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:41 p.m.