Triple
T33647721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norse Rewards |
E862004
|
entity |
| Predicate | travelSector |
P48370
|
FINISHED |
| Object | airline |
—
|
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: airline | Statement: [Norse Rewards, travelSector, airline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: travelSector Context triple: [Norse Rewards, travelSector, airline]
-
A.
travelMarket
chosen
Indicates a relationship where an entity participates in or is associated with the commercial exchange, promotion, or sale of travel-related services or experiences.
-
B.
travelMechanic
Indicates the method or system by which movement or travel between locations is carried out.
-
C.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
D.
tourismType
Indicates the specific category or kind of tourism activity or experience associated with an entity.
-
E.
tourismService
Indicates a relationship where an entity provides or is associated with services intended for tourists, such as travel, accommodation, or guided activities.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:42 a.m.