Triple
T7160693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finnair Plus |
E166933
|
entity |
| Predicate | tierStructure |
P41505
|
FINISHED |
| Object | five main tiers |
—
|
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: five main tiers | Statement: [Finnair Plus, tierStructure, five main tiers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierStructure Context triple: [Finnair Plus, tierStructure, five main tiers]
-
A.
verticalStructure
Indicates a relationship where one entity is a structure that extends predominantly in the vertical direction relative to another reference or context.
-
B.
tierCount
chosen
Indicates the number of distinct levels, ranks, or layers associated with an entity in a hierarchical or tiered structure.
-
C.
titleHierarchy
Indicates a hierarchical relationship between titles, where one title is ranked above or below another in an ordered structure.
-
D.
rankTier
Indicates the classification level or tier assigned to an entity within a ranking or hierarchical system.
-
E.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
- 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_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. |
Created at: March 27, 2026, 2:47 p.m.