Triple
T33812865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On the Run II Tour |
E866586
|
entity |
| Predicate | coHeadliningArtist |
P124505
|
FINISHED |
| Object | Beyoncé |
—
|
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: Beyoncé | Statement: [On the Run II Tour, coHeadliningArtist, Beyoncé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coHeadliningArtist Context triple: [On the Run II Tour, coHeadliningArtist, Beyoncé]
-
A.
headlinedBy
Indicates that something (such as an event, show, or publication) is led, featured, or given top billing by a particular main performer, act, or entity.
-
B.
primaryArtist
Indicates that an entity is the main or lead artist responsible for a creative work, as opposed to supporting or contributing artists.
-
C.
artistOf
Indicates that one entity is the creator or performer responsible for producing a particular work or piece.
-
D.
coArtist
chosen
Indicates that two or more entities collaborate together as artists on the same creative work or project.
-
E.
coverArtistOf
Indicates that one entity is the artist who created the cover artwork for another entity, such as a book, album, or publication.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffcee3a88190951fe0720bfc8fa4 |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.