Triple
T37821847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUN COUNTRY |
E942938
|
entity |
| Predicate | operatorMarketSegment |
P83214
|
FINISHED |
| Object | budget travelers |
—
|
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: budget travelers | Statement: [SUN COUNTRY, operatorMarketSegment, budget travelers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorMarketSegment Context triple: [SUN COUNTRY, operatorMarketSegment, budget travelers]
-
A.
marketSegmentType
Indicates the specific category or segment of the market that an entity, product, or service is targeted toward or associated with.
-
B.
offersMarketSegment
chosen
Indicates that a provider makes a specific market segment available as a target or recipient for its products, services, or offerings.
-
C.
marketSegmentCoverage
Indicates the extent to which a product, service, or campaign reaches or serves the intended market segment(s).
-
D.
governsMarketSegment
Indicates that an entity has controlling influence or regulatory authority over a particular market segment.
-
E.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
- 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_69f76ee987588190906506e759be5db3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a03142a3a7081909bcfb683b44e2217 |
completed | May 12, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_6a031400af808190a72abf095e96c151 |
completed | May 12, 2026, 11:50 a.m. |
Created at: May 3, 2026, 4:19 p.m.