Triple
T11651160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotwire |
E276905
|
entity |
| Predicate | bookingScope |
P80084
|
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: [Hotwire, bookingScope, domestic travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingScope Context triple: [Hotwire, bookingScope, domestic travel]
-
A.
reservationScope
chosen
Indicates the extent or range within which a reservation applies or is valid.
-
B.
promotionScope
Indicates the range or extent within which a promotion or promotional offer is valid or applicable.
-
C.
availabilityScope
Indicates the extent or context within which something is available, accessible, or applicable.
-
D.
locationScope
Indicates the specific geographic or spatial area within which a given relationship, condition, or action is considered valid or applicable.
-
E.
reservationEnclosedBy
Indicates that one reservation is fully contained within the spatial or logical boundaries of another reservation.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a2cea9308190a13f7dd995ea07a4 |
completed | April 10, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.