Triple
T2231408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beach Chalet Soccer Fields |
E48772
|
entity |
| Predicate | bookingRequired |
P19288
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Beach Chalet Soccer Fields, bookingRequired, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingRequired Context triple: [Beach Chalet Soccer Fields, bookingRequired, yes]
-
A.
bookingRequirement
chosen
Indicates that a particular condition, rule, or prerequisite must be satisfied in order to make or confirm a booking.
-
B.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
C.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
D.
mainReservation
Indicates that one reservation is designated as the primary or central booking associated with a person, account, or set of related reservations.
-
E.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06b7374819089fe643e12797bfd |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.