Triple
T33652406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luxair |
E862130
|
entity |
| Predicate | cargoBrand |
P177470
|
FINISHED |
| Object | LuxairCargo |
—
|
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: LuxairCargo | Statement: [Luxair, cargoBrand, LuxairCargo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoBrand Context triple: [Luxair, cargoBrand, LuxairCargo]
-
A.
catalogBrand
Indicates that a brand is associated with, or offered within, a particular catalog.
-
B.
usesRollingStockBrand
Indicates that one entity employs or operates rolling stock manufactured under a specific brand.
-
C.
usesTransportBrand
Indicates that one entity makes use of a transportation service, vehicle, or system associated with a specific brand.
-
D.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
E.
fareBrand
Indicates the specific fare category or brand under which a ticket or booking is sold, defining its associated rules, benefits, and restrictions.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: May 1, 2026, 1:42 a.m.