Triple
T2033923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery Ward |
E44578
|
entity |
| Predicate | brandRevivedAs |
P7738
|
FINISHED |
| Object | online retailer |
—
|
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: online retailer | Statement: [Montgomery Ward, brandRevivedAs, online retailer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandRevivedAs Context triple: [Montgomery Ward, brandRevivedAs, online retailer]
-
A.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
-
B.
brand
Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
-
C.
revivedBy
chosen
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
D.
successorBranding
Indicates that one brand has replaced or continued another brand as its subsequent or updated identity.
-
E.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
- 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb93387488190ac9d8d2746451f2e |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.