Triple
T24203891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Rumble |
E600048
|
entity |
| Predicate | hasBookingPurpose |
P108709
|
FINISHED |
| Object | sets up major storylines for WrestleMania |
—
|
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: sets up major storylines for WrestleMania | Statement: [Royal Rumble, hasBookingPurpose, sets up major storylines for WrestleMania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBookingPurpose Context triple: [Royal Rumble, hasBookingPurpose, sets up major storylines for WrestleMania]
-
A.
bookingPurpose
chosen
Indicates the reason or intended use for which a booking or reservation is made.
-
B.
hasVisitationPurpose
Indicates that an entity’s visit to another entity or location is associated with a specific purpose or reason.
-
C.
hasBookingModel
Indicates that an entity is associated with or uses a particular booking model or reservation scheme.
-
D.
hasReservationOf
Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
-
E.
haveReservation
Indicates that an entity holds or has made a reservation for a service, event, or resource.
- 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_69e288ceaab88190899d0acb5931591d |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27ca38c148190ae65cd692567d43d |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c43e55688190b55fc20274ed471c |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:37 p.m.