Triple
T19961041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IC |
E479813
|
entity |
| Predicate | bookingOptions |
P12821
|
FINISHED |
| Object | online booking |
—
|
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: online booking | Statement: [IC, bookingOptions, online booking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingOptions Context triple: [IC, bookingOptions, online booking]
-
A.
bookingOption
chosen
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.
-
B.
bookingModel
Indicates a relationship where an entity uses or is associated with a specific model or schema that defines how bookings are structured, processed, or represented.
-
C.
bookingHubFor
Indicates that one entity serves as the central platform or system through which bookings or reservations are made for another entity.
-
D.
bookingPattern
Indicates a recurring or characteristic way in which bookings are made, such as their timing, frequency, or sequence.
-
E.
bookingPolicy
Indicates the rules or conditions that govern how bookings or reservations can be made, modified, or canceled 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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65af4520c81909986a47289ba801e |
completed | April 20, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e537f7e4848190b431a69ec3f1b609 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:54 p.m.