Triple
T7160683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnair Plus |
E166933
|
entity |
| Predicate | hasBenefitType |
P75212
|
FINISHED |
| Object | tier benefits |
—
|
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: tier benefits | Statement: [Finnair Plus, hasBenefitType, tier benefits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBenefitType Context triple: [Finnair Plus, hasBenefitType, tier benefits]
-
A.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
isIndividualBenefit
Indicates that something provides a benefit or advantage to a single individual rather than to a group or collective.
-
C.
benefitAdministered
Indicates that a benefit (such as aid, service, or entitlement) has been formally provided or delivered to an eligible recipient by an administering party.
-
D.
criterionForBenefits
Indicates that something serves as a condition or standard that must be met in order for an entity to receive certain benefits.
-
E.
benefitsOrganizationType
Indicates that something provides an advantage, support, or positive impact specifically to a particular type or category of organization.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e82ce770819081dccf7ffd50c2ab |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
| PDg | Predicate description generation | batch_69c6e4a213508190a40aca39f9eee7d5 |
completed | March 27, 2026, 8:12 p.m. |
Created at: March 27, 2026, 2:47 p.m.