Triple
T6177279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TK Maxx |
E137850
|
entity |
| Predicate | reasonForDifferentName |
P2136
|
FINISHED |
| Object | to avoid confusion with existing UK retailer T J Hughes |
—
|
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: to avoid confusion with existing UK retailer T J Hughes | Statement: [TK Maxx, reasonForDifferentName, to avoid confusion with existing UK retailer T J Hughes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForDifferentName Context triple: [TK Maxx, reasonForDifferentName, to avoid confusion with existing UK retailer T J Hughes]
-
A.
reasonForName
Indicates the explanation or cause behind why an entity has a particular name.
-
B.
nameChangeReason
chosen
Indicates the reason or justification for a change in an entity’s name.
-
C.
reasonForNickname
Indicates the explanation or cause behind why a particular nickname was given to an entity.
-
D.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
-
E.
nameContrastsWith
Indicates that one name is deliberately chosen or used to highlight a difference or opposition in meaning, style, or identity relative to another name.
- 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_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. |
Created at: March 22, 2026, 4:18 p.m.