Triple
T2164012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ADA paratransit |
E46866
|
entity |
| Predicate | hasBookingModel |
P36101
|
FINISHED |
| Object | reservation-based service |
—
|
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: reservation-based service | Statement: [ADA paratransit, hasBookingModel, reservation-based service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBookingModel Context triple: [ADA paratransit, hasBookingModel, reservation-based service]
-
A.
hasBookingChannel
Indicates that an entity is associated with or obtained through a particular method or platform used to make a booking.
-
B.
containsReservation
Indicates that one entity includes or holds a reservation associated with another entity.
-
C.
hasCheckInSystem
Indicates that an entity uses or is equipped with a system for registering or recording check-ins.
-
D.
hasReservationPolicy
Indicates that an entity specifies or is governed by a particular policy regarding how reservations are made, managed, or honored.
-
E.
hasAccommodation
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
- 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_69a88a184cbc8190877791f6552c2484 |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe8e1cfc81908adc0357ddfec701 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbe1ecb7081909c2c66da08a48ab7 |
completed | March 7, 2026, 5:56 a.m. |
Created at: March 4, 2026, 7:45 p.m.