Triple
T3803352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flair Airlines |
E91741
|
entity |
| Predicate | ticketDistributionChannel |
P35642
|
FINISHED |
| Object | direct online sales |
—
|
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: direct online sales | Statement: [Flair Airlines, ticketDistributionChannel, direct online sales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketDistributionChannel Context triple: [Flair Airlines, ticketDistributionChannel, direct online sales]
-
A.
distributionBy
Indicates how something is allocated, arranged, or spread according to a specified criterion or grouping.
-
B.
distributorType
Indicates the specific category or role of a distributor in relation to the distribution of a product or service.
-
C.
distributesIn
Indicates that one entity allocates or hands out something (e.g., items, resources, information) within or across a specified area, group, or context.
-
D.
salesChannels
chosen
Indicates the channels or methods through which a product or service is marketed, sold, or distributed to customers.
-
E.
distributor
Indicates that an entity is responsible for supplying, delivering, or making another entity’s products or materials available to others.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.