Triple
T31846289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HM-B |
E812950
|
entity |
| Predicate | underlyingCompanySubSector |
P6744
|
FINISHED |
| Object | Specialty Retail |
—
|
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: Specialty Retail | Statement: [HM-B, underlyingCompanySubSector, Specialty Retail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingCompanySubSector Context triple: [HM-B, underlyingCompanySubSector, Specialty Retail]
-
A.
industryOfUnderlyingCompany
chosen
Indicates the industry sector in which the underlying company associated with this entity operates.
-
B.
underlyingCompanyType
Indicates the classification or category of company that forms the basis or source for another related entity or instrument.
-
C.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
D.
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.
-
E.
subsidiaryIndustry
Indicates that a subsidiary company operates within or is associated with a particular industry sector.
- 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_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 30, 2026, 11:50 p.m.