Triple
T29720434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK 2015 Face the Music Tour (live releases) |
E752041
|
entity |
| Predicate | tourNameReferenced |
P86144
|
FINISHED |
| Object | Face the Music |
—
|
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: Face the Music | Statement: [UK 2015 Face the Music Tour (live releases), tourNameReferenced, Face the Music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourNameReferenced Context triple: [UK 2015 Face the Music Tour (live releases), tourNameReferenced, Face the Music]
-
A.
tourNameDerivedFrom
chosen
Indicates that the name of a tour is derived from, or based on, another specified source or entity.
-
B.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
C.
tourComponentOf
Indicates that something functions as a constituent part or segment of a larger tour.
-
D.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
E.
tourStaple
Indicates that something is a standard, frequently included element or highlight of a 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 28, 2026, 7:36 p.m.