Triple
T6177267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TK Maxx |
E137850
|
entity |
| Predicate | productSourcingStrategy |
P69263
|
FINISHED |
| Object | opportunistic buying |
—
|
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: opportunistic buying | Statement: [TK Maxx, productSourcingStrategy, opportunistic buying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productSourcingStrategy Context triple: [TK Maxx, productSourcingStrategy, opportunistic buying]
-
A.
purchaseMethod
Indicates the way or channel through which a purchase is made (e.g., online, in-store, by phone, or via a specific payment or ordering method).
-
B.
brandSource
Indicates that one entity is the originating or providing brand associated with another entity (such as a product, service, or content).
-
C.
procurementPartner
Indicates that one entity serves as a supplier or provider responsible for acquiring goods or services on behalf of another entity.
-
D.
supplyRole
Indicates that an entity provides or fulfills a specific role within a supply or provisioning relationship to another entity.
-
E.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
- 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_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc87bc48190834042d9c41d5b86 |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.