Triple
T195972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiffany & Co. flagship store |
E3819
|
entity |
| Predicate | clientele |
P481
|
FINISHED |
| Object | high-end consumers |
—
|
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: high-end consumers | Statement: [Tiffany & Co. flagship store, clientele, high-end consumers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clientele Context triple: [Tiffany & Co. flagship store, clientele, high-end consumers]
-
A.
customerType
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
B.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
C.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
D.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
-
E.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
- 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a25983b49c819080f7e161904c53da |
completed | Feb. 28, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69a25677da14819094cd02868fd30c83 |
completed | Feb. 28, 2026, 2:44 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.