Triple
T9391378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad World Tour |
E226032
|
entity |
| Predicate | numberOfShowsAtVenue |
P25315
|
FINISHED |
| Object | 7 at Wembley Stadium, London |
—
|
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: 7 at Wembley Stadium, London | Statement: [Bad World Tour, numberOfShowsAtVenue, 7 at Wembley Stadium, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfShowsAtVenue Context triple: [Bad World Tour, numberOfShowsAtVenue, 7 at Wembley Stadium, London]
-
A.
numberOfShows
chosen
Indicates the total count of shows associated with or performed by a given entity.
-
B.
numberOfVenues
Indicates the total count of venues associated with a given entity or context.
-
C.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
D.
homeVenueAppearances
Indicates the number of times an entity has appeared or performed at its designated home venue.
-
E.
connectsToEventVenue
Indicates that one entity serves as a link or route providing access or connection to an event venue.
- 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_69ca842f7e3481908bf5bcf52e032dbd |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd510eae0c8190b7c4ab487a366bb3 |
completed | April 1, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69cca545b2448190a4297312e39c21ac |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.