Triple
T5972654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruda |
E132910
|
entity |
| Predicate | hasBrandEvolutionStage |
P45325
|
FINISHED |
| Object | early name of Puma brand |
—
|
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: early name of Puma brand | Statement: [Ruda, hasBrandEvolutionStage, early name of Puma brand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrandEvolutionStage Context triple: [Ruda, hasBrandEvolutionStage, early name of Puma brand]
-
A.
brandEvolution
chosen
Indicates how a brand’s identity, positioning, or attributes change and develop over time.
-
B.
hasFormerLogo
Indicates that an entity is associated with a logo it used in the past but no longer uses.
-
C.
companyEvolvedInto
Indicates that one company has transformed, restructured, or transitioned over time into another company, representing a continuity of organizational identity or operations.
-
D.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
E.
introducedAsBrandBy
Indicates that one entity was presented or launched to the public or a market as a brand 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_69c0086deab081908550159ca23eec9b |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04dc2243c8190bd3488e7b24af985 |
completed | March 22, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69c049dcb3c081908ccc9b4d4b210229 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:03 p.m.