Triple
T21460404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Butterfly World Tour |
E529452
|
entity |
| Predicate | hasLeadPerformerRole |
P9640
|
FINISHED |
| Object | lead vocalist |
—
|
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: lead vocalist | Statement: [Butterfly World Tour, hasLeadPerformerRole, lead vocalist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeadPerformerRole Context triple: [Butterfly World Tour, hasLeadPerformerRole, lead vocalist]
-
A.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
B.
hasArtistRole
chosen
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
C.
performerOn
Indicates that an entity serves as the performer or executing agent of an action, event, or work associated with another entity.
-
D.
replacesInLeadRole
Indicates that one entity takes over or substitutes for another entity in the primary or leading role within a given context or production.
-
E.
hasNotablePerformer
Indicates that an entity features or is associated with a performer who is particularly prominent, famous, or otherwise noteworthy.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ee10ec8190a606aa64001af35e |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.