Triple
T1543479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Business Select |
E32922
|
entity |
| Predicate | fareRules |
P9545
|
FINISHED |
| Object | subject to Southwest Airlines Contract of Carriage |
—
|
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: subject to Southwest Airlines Contract of Carriage | Statement: [Business Select, fareRules, subject to Southwest Airlines Contract of Carriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fareRules Context triple: [Business Select, fareRules, subject to Southwest Airlines Contract of Carriage]
-
A.
farePolicySupport
Indicates that there is a policy in place governing fares (such as prices, discounts, or rules) that is recognized, enabled, or supported in the given context.
-
B.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
C.
venuePolicy
Indicates the rules or guidelines that govern how activities or events may be conducted at a particular venue.
-
D.
fareDiscount
Indicates that a reduced price is applied to a standard fare for a product or service.
-
E.
fareBasis
chosen
Indicates the specific fare rule or pricing category that applies to a ticket or travel segment.
- 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_69a885ed29088190a3c2d5a3d100c16e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa95c1a2948190a2b98469afec1a7d |
completed | March 6, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69a907b2453c8190a41f6b88c8217d1e |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:26 p.m.