Triple
T8362929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ola |
E197052
|
entity |
| Predicate | supportsBookingType |
P45275
|
FINISHED |
| Object | immediate rides |
—
|
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: immediate rides | Statement: [Ola, supportsBookingType, immediate rides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBookingType Context triple: [Ola, supportsBookingType, immediate rides]
-
A.
alsoBookableAs
Indicates that one entity can be reserved or booked in an alternative way or under an alternative option represented by another entity.
-
B.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
-
C.
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.
-
D.
hasReservationType
chosen
Indicates that an entity is associated with a specific category or type of reservation.
-
E.
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.
- 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_69ca82f2dbe48190aba982e75a0d94de |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80768b208190a5f6c9e6cb6e7f30 |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6 p.m.