Triple
T31003626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easy family of companies |
E790005
|
entity |
| Predicate | hasLegalOwnerOfBrand |
P192304
|
FINISHED |
| Object | easyGroup IP Licensing Ltd |
—
|
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: easyGroup IP Licensing Ltd | Statement: [easy family of companies, hasLegalOwnerOfBrand, easyGroup IP Licensing Ltd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalOwnerOfBrand Context triple: [easy family of companies, hasLegalOwnerOfBrand, easyGroup IP Licensing Ltd]
-
A.
ownsLicensesUnderBrand
Indicates that one entity holds or possesses licenses that are issued under, associated with, or governed by a particular brand.
-
B.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
C.
brandLicenseFrom
Indicates that one entity holds a licensed right to use the brand owned or controlled by another entity.
-
D.
brandOwnerInstanceOf
Indicates that a specific brand owner is an instance of a particular class or type of brand-owning entity.
-
E.
hasBrandOwnerTicker
Indicates that an entity is associated with the stock ticker symbol of the company that owns its brand.
- 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_69f224c65a348190baaed1c01a29900c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 29, 2026, 8:57 p.m.