Triple
T33550866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sticky & Sweet Tour |
E859326
|
entity |
| Predicate | succeededByTour |
P95614
|
FINISHED |
| Object | The MDNA Tour |
—
|
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: The MDNA Tour | Statement: [Sticky & Sweet Tour, succeededByTour, The MDNA Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: succeededByTour Context triple: [Sticky & Sweet Tour, succeededByTour, The MDNA Tour]
-
A.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
B.
followsTour
chosen
Indicates that one entity attends or participates in a tour that occurs after, or as a consequence of, another specified event or tour.
-
C.
previousTour
Indicates that one entity represents a tour that occurred before another tour in a sequence or timeline.
-
D.
performedTour
Indicates that an entity carried out or conducted a tour for another entity or at a particular place and time.
-
E.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:39 a.m.