Triple
T34394733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KrisFlyer Elite Silver |
E882798
|
entity |
| Predicate | statusBenefitsType |
P66311
|
FINISHED |
| Object | priority services |
—
|
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: priority services | Statement: [KrisFlyer Elite Silver, statusBenefitsType, priority services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBenefitsType Context triple: [KrisFlyer Elite Silver, statusBenefitsType, priority services]
-
A.
beneficeType
Indicates the specific category or kind of benefice (ecclesiastical office or endowed church position) associated with an entity.
-
B.
benefitsLevel
Indicates the degree or extent to which one entity gains advantages, support, or positive outcomes from another entity or action.
-
C.
benefitMode
Indicates the manner or method through which a benefit is provided, received, or realized in the relationship.
-
D.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
E.
benefitsAre
chosen
Indicates that certain advantages, gains, or positive outcomes are possessed by or accrue to a particular entity or group.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: May 1, 2026, 1:59 a.m.