Triple
T10413862
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAS EuroBonus Gold |
E245463
|
entity |
| Predicate | eligiblePassengerType |
P15253
|
FINISHED |
| Object | individual traveler |
—
|
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: individual traveler | Statement: [SAS EuroBonus Gold, eligiblePassengerType, individual traveler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligiblePassengerType Context triple: [SAS EuroBonus Gold, eligiblePassengerType, individual traveler]
-
A.
hasPassengerRole
chosen
Indicates that an entity participates in a context or event specifically in the capacity or role of a passenger.
-
B.
passengerAccess
Indicates that a passenger is allowed to enter, use, or move through a particular vehicle, area, or transportation-related facility.
-
C.
hasBoardingType
Indicates the specific manner or method by which an entity is boarded or accessed (e.g., how passengers or items are taken on).
-
D.
isPassengerOnly
Indicates that the subject entity is restricted to passenger use only and does not accommodate cargo, freight, or mixed-use purposes.
-
E.
hasPassengerCheckInAccess
Indicates that an entity is permitted to perform or access passenger check-in functions for a given transport service or location.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.