Triple
T37159484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kodak Carousel pitch |
E920605
|
entity |
| Predicate | rebrandsProductAs |
P68192
|
FINISHED |
| Object | “Carousel” instead of “wheel” |
—
|
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: “Carousel” instead of “wheel” | Statement: [Kodak Carousel pitch, rebrandsProductAs, “Carousel” instead of “wheel”]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebrandsProductAs Context triple: [Kodak Carousel pitch, rebrandsProductAs, “Carousel” instead of “wheel”]
-
A.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
brandingReplaced
Indicates that one branding has been superseded or substituted by another branding.
-
C.
rebrandedReason
Indicates the reason or motivation for which an entity underwent a rebranding.
-
D.
rebrandingProgram
Indicates a program or initiative through which an entity changes or updates its brand identity, such as its name, logo, or overall image.
-
E.
productRenamedAs
chosen
Indicates that a product previously known by one name is now identified or marketed under a new name.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.