Triple
T31003500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easyGroup Holdings Limited |
E790002
|
entity |
| Predicate | brandFamilyIncludes |
P65067
|
FINISHED |
| Object | easyJet |
—
|
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: easyJet | Statement: [easyGroup Holdings Limited, brandFamilyIncludes, easyJet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandFamilyIncludes Context triple: [easyGroup Holdings Limited, brandFamilyIncludes, easyJet]
-
A.
brandIncludes
chosen
Indicates that a broader brand or brand portfolio encompasses, owns, or contains the specified sub-brand, product line, or branded entity.
-
B.
usesSameBrandFamilyAs
Indicates that two entities use products or services belonging to the same overarching brand family or brand portfolio.
-
C.
productFamily
Indicates that one product belongs to, or is categorized under, a broader product family or line.
-
D.
catalogueFamily
Indicates a relationship where an entity is grouped into or associated with a particular catalogue family or classification set.
-
E.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 29, 2026, 8:57 p.m.