Triple
T31846304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HM-B |
E812950
|
entity |
| Predicate | underlyingCompanyOtherBrands |
P10460
|
FINISHED |
| Object | COS |
—
|
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: COS | Statement: [HM-B, underlyingCompanyOtherBrands, COS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanyOtherBrands Context triple: [HM-B, underlyingCompanyOtherBrands, COS]
-
A.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
B.
underlyingCompanyAlsoProduces
Indicates that the same underlying company is responsible for producing both of the related entities.
-
C.
underlyingCompany
Indicates that one entity serves as the fundamental or base company upon which another entity (such as a product, instrument, or structure) is built, derived, or dependent.
-
D.
underlyingCompanyName
Indicates the name of the company that serves as the foundational or primary entity underlying another entity, structure, or instrument.
-
E.
relatedBrand
chosen
Indicates a relationship where one brand is associated with, connected to, or otherwise related to another 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_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: April 30, 2026, 11:50 p.m.