Triple
T13184971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFM |
E313824
|
entity |
| Predicate | hasParentBrandElement |
P108944
|
FINISHED |
| Object | Nebraska Furniture Mart stores |
—
|
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: Nebraska Furniture Mart stores | Statement: [NFM, hasParentBrandElement, Nebraska Furniture Mart stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentBrandElement Context triple: [NFM, hasParentBrandElement, Nebraska Furniture Mart stores]
-
A.
hasUnderlyingCompanyBrand
Indicates that one entity is associated with or operates under the corporate brand of another company as its underlying brand.
-
B.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
C.
hasParentCategory
Indicates that an entity belongs to or is organized under a broader, more general category.
-
D.
hasBrandIdentityElement
Indicates that an entity includes or is associated with a specific component of its overall brand identity (such as a logo, color scheme, or tagline).
-
E.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98ceeb22c8190a6be666031d9e5a4 |
completed | April 10, 2026, 11:51 p.m. |
Created at: April 9, 2026, 9:15 p.m.