Triple
T24974233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | co-founding Reebok |
E624973
|
entity |
| Predicate | hasBrandCreated |
P159399
|
FINISHED |
| Object | Reebok |
—
|
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: Reebok | Statement: [co-founding Reebok, hasBrandCreated, Reebok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandCreated Context triple: [co-founding Reebok, hasBrandCreated, Reebok]
-
A.
hasBrandName
Indicates that an entity is associated with or identified by a specific brand name.
-
B.
hasBrandRole
Indicates that an entity holds a specific functional or organizational role in relation to a particular brand.
-
C.
hasBrandType
Indicates that an entity is associated with or categorized under a particular brand type or classification.
-
D.
hasBranding
Indicates that one entity carries, displays, or is associated with the brand identity of another entity.
-
E.
hasBrandConcept
Indicates that an entity is associated with or embodies a particular brand concept or branding idea.
- F. None of above. chosen
Provenance (4 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_69f584f07b648190aee894c1d5320bc3 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f55e497fa081909bc59a7b92c5df59 |
completed | May 2, 2026, 2:15 a.m. |
Created at: April 18, 2026, 6:01 a.m.