Triple
T29071157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born This Way Ball |
E735815
|
entity |
| Predicate | nextTour |
P114858
|
FINISHED |
| Object | ArtRave: The Artpop Ball |
—
|
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: ArtRave: The Artpop Ball | Statement: [Born This Way Ball, nextTour, ArtRave: The Artpop Ball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nextTour Context triple: [Born This Way Ball, nextTour, ArtRave: The Artpop Ball]
-
A.
previousTour
chosen
Indicates that one entity represents a tour that occurred before another tour in a sequence or timeline.
-
B.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
-
C.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
D.
nextTournament
Indicates that one entity is the immediately upcoming tournament scheduled to occur for the other entity.
-
E.
followsTour
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
- 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_69f077e9b0a48190bb79548279cb7f64 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f660fa7f408190a99ed988d652f73f |
completed | May 2, 2026, 8:39 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:20 a.m.