Triple
T31003627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | easy family of companies |
E790005
|
entity |
| Predicate | hasBrandController |
P58599
|
FINISHED |
| Object | easyGroup |
—
|
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 | Statement: [easy family of companies, hasBrandController, easyGroup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandController Context triple: [easy family of companies, hasBrandController, easyGroup]
-
A.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
B.
controlsBrand
chosen
Indicates that one entity has authority over, management of, or decisive influence on the brand of another entity.
-
C.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
D.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
-
E.
hasCoreBrand
Indicates that one entity possesses, is associated with, or is defined by a primary or central brand.
- 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_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: April 29, 2026, 8:57 p.m.