Triple
T31846297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HM-B |
E812950
|
entity |
| Predicate | underlyingBrandWebsite |
P13482
|
FINISHED |
| Object | https://www.hm.com |
—
|
LITERAL FINISHED |
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: https://www.hm.com | Statement: [HM-B, underlyingBrandWebsite, https://www.hm.com]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingBrandWebsite Context triple: [HM-B, underlyingBrandWebsite, https://www.hm.com]
-
A.
hasBrandWebsite
Indicates that an entity has an associated official website representing its brand.
-
B.
hasCorporateWebsiteOfUnderlyingCompany
Indicates that an entity has a corporate website corresponding to the underlying company associated with it.
-
C.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
-
D.
hasUnderlyingWebsite
chosen
Indicates that one entity is supported, represented, or implemented by another entity that functions as its underlying website.
-
E.
nowUnderBrand
Indicates that an entity is currently operating, marketed, or managed under a specified 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: April 30, 2026, 11:50 p.m.