Triple
T2079671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neiman Marcus Group |
E45208
|
entity |
| Predicate | salesChannels |
P35642
|
FINISHED |
| Object | brick-and-mortar 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: brick-and-mortar stores | Statement: [Neiman Marcus Group, salesChannels, brick-and-mortar stores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salesChannels Context triple: [Neiman Marcus Group, salesChannels, brick-and-mortar stores]
-
A.
saleType
Indicates the specific category or method by which a sale is conducted or classified (e.g., retail, wholesale, auction).
-
B.
salesWorldwide
Indicates a relationship where an entity’s sales figures or activities are measured, reported, or occur across multiple countries or global markets.
-
C.
soldAt
Indicates that a product or item is offered for sale at a particular location, venue, or outlet.
-
D.
salesUS
Indicates a relationship where sales activity, revenue, or transactions are specifically associated with the United States.
-
E.
soldByDivision
Indicates that an item, product, or service is sold by a specific division within an organization.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba3307308190ab329fe3192b2e0f |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.