Triple
T33653455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOT Miles & More Frequent Traveller |
E862158
|
entity |
| Predicate | statusBrand |
P133890
|
FINISHED |
| Object | Miles & More |
—
|
NE NERFINISHED |
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: Miles & More | Statement: [LOT Miles & More Frequent Traveller, statusBrand, Miles & More]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusBrand Context triple: [LOT Miles & More Frequent Traveller, statusBrand, Miles & More]
-
A.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
-
B.
isBrand
chosen
Indicates that one entity functions as the commercial brand or label associated with another entity.
-
C.
controlsBrand
Indicates that one entity has authority over, management of, or decisive influence on the brand of another entity.
-
D.
brandNumber
Indicates the identifying number or code assigned to a particular brand within a system or dataset.
-
E.
exportBrand
Indicates a relationship where a brand is sold or distributed outside its home market into foreign or international markets.
- 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_69ff109695008190a22b47ef8be2e3f9 |
completed | May 9, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69ff0f243ea88190970d2c520b55c816 |
completed | May 9, 2026, 10:40 a.m. |
Created at: May 1, 2026, 1:42 a.m.