Triple
T33007668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DW Sports Fitness |
E844552
|
entity |
| Predicate | hasNumberOfRetailStoresAtPeak |
P8902
|
FINISHED |
| Object | around 50 |
—
|
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: around 50 | Statement: [DW Sports Fitness, hasNumberOfRetailStoresAtPeak, around 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfRetailStoresAtPeak Context triple: [DW Sports Fitness, hasNumberOfRetailStoresAtPeak, around 50]
-
A.
hasRetailStores
Indicates that an entity operates or possesses one or more physical retail store locations.
-
B.
hasRetailPresenceIn
Indicates that an entity conducts retail operations or maintains a retail outlet, store, or sales presence within a specified location.
-
C.
hasRetailHistory
Indicates that an entity has a past record of involvement in retail activities, such as operating, selling, or transacting in retail contexts.
-
D.
numberOfStores
chosen
Indicates the total count of stores associated with a given entity or context.
-
E.
hasRetailBoutiquesIn
Indicates that an entity operates or maintains retail boutiques located within a specified place or region.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe5c1a502081909d4024e514309c8e |
completed | May 8, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69fe5a9df21c819087153f5d0bcaa987 |
completed | May 8, 2026, 9:50 p.m. |
Created at: May 1, 2026, 1:23 a.m.