Triple
T24974251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | co-founding Reebok |
E624973
|
entity |
| Predicate | hasGrowthPhase |
P24285
|
FINISHED |
| Object | rapid expansion in the 1980s |
—
|
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: rapid expansion in the 1980s | Statement: [co-founding Reebok, hasGrowthPhase, rapid expansion in the 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrowthPhase Context triple: [co-founding Reebok, hasGrowthPhase, rapid expansion in the 1980s]
-
A.
hasGrowthRate
Indicates the rate at which something increases in size, quantity, or value over a given period of time.
-
B.
hadGrowthPeriod
chosen
Indicates that an entity experienced a specific span of time during which it underwent growth or development.
-
C.
hasSecondaryGrowth
Indicates that an organism or structure undergoes secondary growth, meaning it increases in thickness or girth after its initial (primary) growth phase.
-
D.
growthStatus
Indicates the current stage or condition of development or progress of an entity over time.
-
E.
isGrowingAs
Indicates that one entity is developing, evolving, or increasing in some capacity in the manner or role specified by another entity.
- 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_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:01 a.m.