Triple
T37821827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SUN COUNTRY |
E942938
|
entity |
| Predicate | operatorBusinessFocus |
P204036
|
FINISHED |
| Object | leisure 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: leisure travel | Statement: [SUN COUNTRY, operatorBusinessFocus, leisure travel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorBusinessFocus Context triple: [SUN COUNTRY, operatorBusinessFocus, leisure travel]
-
A.
businessModelFocus
Indicates that one entity’s business model is centered on, tailored to, or primarily oriented around another entity or specific focus area.
-
B.
underlyingCompanyBusinessFocus
Indicates the primary industry, sector, or type of business activity that the underlying company is focused on.
-
C.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
D.
businessFunction
Indicates the specific role, activity, or operational function that an entity performs within a business context.
-
E.
businessOrigin
Indicates the place, source, or context from which a business or commercial entity originates or was established.
- F. None of above. chosen
Provenance (4 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_6a030f1480148190a5e8c8926ded252c |
completed | May 12, 2026, 11:29 a.m. |
| PD | Predicate disambiguation | batch_6a030e7f5fa481909696733defefcc20 |
completed | May 12, 2026, 11:26 a.m. |
| PDg | Predicate description generation | batch_6a030f139b688190b3611d96b091c09e |
completed | May 12, 2026, 11:29 a.m. |
Created at: May 3, 2026, 4:19 p.m.