Triple
T7971045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Individual Lightning Lane purchases |
E185322
|
entity |
| Predicate | reservationScope |
P80084
|
FINISHED |
| Object | one attraction per purchase |
—
|
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: one attraction per purchase | Statement: [Individual Lightning Lane purchases, reservationScope, one attraction per purchase]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationScope Context triple: [Individual Lightning Lane purchases, reservationScope, one attraction per purchase]
-
A.
reservationProvision
Indicates that one entity provides, allocates, or sets aside a reservation (such as a booked resource, service slot, or capacity) for another entity.
-
B.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
-
C.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
D.
reservationPolicy
Indicates the rules or conditions governing how reservations are made, modified, or canceled between parties.
-
E.
reservationEstablished
Indicates that a reservation has been successfully created and confirmed between the involved parties or systems.
- F. None of above. chosen
Provenance (4 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_69ca8297699481909b75a405f01e03af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3bd476108190988a75653a5c56d6 |
completed | March 31, 2026, 3:13 a.m. |
| PD | Predicate disambiguation | batch_69cb047a8e4c81909b79e0f0bf56440c |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:13 p.m.