Triple
T26830078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lady’s World |
E675475
|
entity |
| Predicate | wasRebrandedAs |
P1501
|
FINISHED |
| Object | Woman’s World |
—
|
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: Woman’s World | Statement: [The Lady’s World, wasRebrandedAs, Woman’s World]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRebrandedAs Context triple: [The Lady’s World, wasRebrandedAs, Woman’s World]
-
A.
announcedRebrandingAs
Indicates that one entity has publicly declared it will change its name, brand, or identity to that of another entity.
-
B.
formerBrand
chosen
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
C.
rebrandedYear
Indicates the year in which an entity changed its brand identity, such as its name, logo, or overall branding.
-
D.
renamedCompanyAs
Indicates that one company has changed its official name to another specified company name.
-
E.
renamedCompany
Indicates that an existing company has changed its name to a new company name or identity.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61adc60c88190924d7b71d52851e8 |
completed | May 2, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5 a.m.