Triple
T33007667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DW Sports Fitness |
E844552
|
entity |
| Predicate | hasNumberOfGymsAtPeak |
P165818
|
FINISHED |
| Object | around 75 |
—
|
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 75 | Statement: [DW Sports Fitness, hasNumberOfGymsAtPeak, around 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfGymsAtPeak Context triple: [DW Sports Fitness, hasNumberOfGymsAtPeak, around 75]
-
A.
numberOfLocationsAtPeak
Indicates the total count of distinct locations associated with an entity at its highest or peak point in time or activity.
-
B.
hasGymLeader
Indicates that an entity (such as a location or organization) has a specific gym leader associated with it as its primary trainer or authority figure.
-
C.
hasNumberAtPeak
chosen
Indicates that an entity possesses a specific numerical value measured at its highest or peak point.
-
D.
hasNumberOfSeatsAtPeak
Indicates the maximum number of seats available or occupied at the peak usage or capacity of something.
-
E.
hasPokémonLeagueLocation
Indicates that a Pokémon League is situated at or associated with a specific geographic location.
- 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_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: May 1, 2026, 1:23 a.m.