Triple
T38255017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbitz |
E1017761
|
entity |
| Predicate | supportsBookingFor |
P92838
|
FINISHED |
| Object | domestic travel |
—
|
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: domestic travel | Statement: [Orbitz, supportsBookingFor, domestic travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBookingFor Context triple: [Orbitz, supportsBookingFor, domestic travel]
-
A.
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.
-
B.
allowsReservation
Indicates that one entity permits another entity to make or hold a reservation for its use or access.
-
C.
alsoBookableAs
Indicates that one entity can be reserved or booked in an alternative way or under an alternative option represented by another entity.
-
D.
supportsMeetingsOf
Indicates that one entity provides the necessary functionality or resources to enable or host the meetings of another entity.
-
E.
bookingHubFor
chosen
Indicates that one entity serves as the central platform or system through which bookings or reservations are made for another entity.
- 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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.