Triple
T33653456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOT Miles & More Frequent Traveller |
E862158
|
entity |
| Predicate | statusLinkedTo |
P45754
|
FINISHED |
| Object | LOT Polish Airlines brand |
—
|
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: LOT Polish Airlines brand | Statement: [LOT Miles & More Frequent Traveller, statusLinkedTo, LOT Polish Airlines brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusLinkedTo Context triple: [LOT Miles & More Frequent Traveller, statusLinkedTo, LOT Polish Airlines brand]
-
A.
associatedStatus
chosen
Indicates that one entity is linked to or characterized by a particular status or condition.
-
B.
hasBeenLinkedTo
Indicates that an entity has been associated or connected with another entity, often suggesting a reported or inferred relationship between them.
-
C.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
D.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
E.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: May 1, 2026, 1:42 a.m.