Triple
T15130143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oasis Canteen |
E361395
|
entity |
| Predicate | reservationsAccepted |
P42570
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Oasis Canteen, reservationsAccepted, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservationsAccepted Context triple: [Oasis Canteen, reservationsAccepted, false]
-
A.
allowsReservationsOn
Indicates that one entity permits making reservations or bookings for another entity.
-
B.
allowsReservation
chosen
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
-
C.
hasReservationOf
Indicates that one entity holds or possesses a reservation for another entity (such as a service, resource, or event).
-
D.
hasReservationFor
Indicates that an entity holds or is associated with a reservation for a specific event, service, or resource.
-
E.
hasReservationIn
Indicates that an entity holds or possesses a reservation at or within a specified place, service, or event.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b194748190801e3956bf2429d4 |
completed | April 15, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69deb9713fe881909dec2fd3f6c84b39 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:06 a.m.