Triple
T33007684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DW Sports Fitness |
E844552
|
entity |
| Predicate | parentCompanyBeforeAdministration |
P5815
|
FINISHED |
| Object | DW Sports Ltd |
—
|
NE NERFINISHED |
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: DW Sports Ltd | Statement: [DW Sports Fitness, parentCompanyBeforeAdministration, DW Sports Ltd]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentCompanyBeforeAdministration Context triple: [DW Sports Fitness, parentCompanyBeforeAdministration, DW Sports Ltd]
-
A.
parentCompanyAtStartOfPeriod
Indicates that one entity was the parent company of another at the beginning of a specified time period.
-
B.
formerParentCompany
chosen
Indicates that one entity previously served as the parent company of another but no longer holds that status.
-
C.
parentCompanyAtTime
Indicates that one company is the parent (controlling) company of another during a specified time period.
-
D.
predecessorCompany
Indicates that one company previously existed in a role or form that was succeeded or replaced by another company.
-
E.
parentCompanyDuringOperation
Indicates that one company functioned as the parent company of another during the time a specific operation or activity was taking place.
- 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_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 1, 2026, 1:23 a.m.