Triple
T4707587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 47th Street Diamond District |
E104427
|
entity |
| Predicate | majorCustomerType |
P809
|
FINISHED |
| Object | wholesale buyers |
—
|
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: wholesale buyers | Statement: [47th Street Diamond District, majorCustomerType, wholesale buyers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorCustomerType Context triple: [47th Street Diamond District, majorCustomerType, wholesale buyers]
-
A.
majorCustomer
Indicates that one entity is a primary or high-value customer of another entity, typically contributing a significant portion of business or revenue.
-
B.
customerType
chosen
Indicates the classification or category assigned to a customer based on their characteristics, status, or relationship with a business.
-
C.
secondaryCustomer
Indicates a relationship where one customer is designated as an additional or subordinate customer associated with a primary customer in a given context.
-
D.
majorConstituentType
Indicates the type or category of a primary or dominant component that makes up a larger whole.
-
E.
exportCustomer
Indicates initiating the transfer or output of customer-related data from one system or context to another, typically for integration, backup, or reporting purposes.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:17 p.m.