Triple
T24974254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | co-founding Reebok |
E624973
|
entity |
| Predicate | hasOwnershipChange |
P147227
|
FINISHED |
| Object | acquisition by Adidas in 2006 |
—
|
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: acquisition by Adidas in 2006 | Statement: [co-founding Reebok, hasOwnershipChange, acquisition by Adidas in 2006]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOwnershipChange Context triple: [co-founding Reebok, hasOwnershipChange, acquisition by Adidas in 2006]
-
A.
ownershipChangeResult
chosen
Indicates the outcome or resulting state produced by a change in ownership between entities.
-
B.
hasOwnerAction
Indicates that an owner performs, initiates, or is responsible for a specific action related to the owned entity.
-
C.
hasPolicyChange
Indicates that a change has been made to an existing policy or set of policies affecting the related entities.
-
D.
hasMemberChange
Indicates that a change has occurred in the membership of a group, organization, or collection, such as members being added, removed, or modified.
-
E.
hasChangeControl
Indicates that an entity is subject to a defined process for reviewing, approving, and managing modifications or updates.
- 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_69e2ff24512481908e9a72315b8d0354 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f4490283c481908c18246dc7125eec |
completed | May 1, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:01 a.m.