Triple
T28994698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hold the Girl Tour |
E736122
|
entity |
| Predicate | hasSetlistFeaturing |
P33226
|
FINISHED |
| Object | Hold the Girl (song) |
—
|
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: Hold the Girl (song) | Statement: [Hold the Girl Tour, hasSetlistFeaturing, Hold the Girl (song)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetlistFeaturing Context triple: [Hold the Girl Tour, hasSetlistFeaturing, Hold the Girl (song)]
-
A.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
B.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
C.
setlistCharacteristic
Indicates that a particular property or feature characterizes or describes a musical setlist.
-
D.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
E.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 28, 2026, 9:29 a.m.