Triple
T31860086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mylo Xyloto Tour |
E813303
|
entity |
| Predicate | audienceInteractionElement |
P45833
|
FINISHED |
| Object | Xylobands |
—
|
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: Xylobands | Statement: [Mylo Xyloto Tour, audienceInteractionElement, Xylobands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceInteractionElement Context triple: [Mylo Xyloto Tour, audienceInteractionElement, Xylobands]
-
A.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
B.
intendedAudienceInteraction
Indicates that one entity is the target group or audience with whom another entity is meant to interact or engage.
-
C.
interactiveElement
Indicates that one entity functions as an interface component designed to receive and respond to user actions initiated by another entity.
-
D.
engagesAudienceAs
Indicates that one entity actively captures, involves, or holds the attention of an audience in the manner or role specified by another entity.
-
E.
audienceSetting
Indicates the context or environment in which an audience is situated or addressed.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b06e4cc48190bed5ef29ed8ebf3f |
completed | May 3, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:53 p.m.