Triple
T22863132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterford Wedgwood plc |
E566977
|
entity |
| Predicate | notableBrandSpeciality |
P60713
|
FINISHED |
| Object | Waterford crystal glassware |
—
|
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: Waterford crystal glassware | Statement: [Waterford Wedgwood plc, notableBrandSpeciality, Waterford crystal glassware]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBrandSpeciality Context triple: [Waterford Wedgwood plc, notableBrandSpeciality, Waterford crystal glassware]
-
A.
notableBrandElement
chosen
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
B.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
C.
popularBrand
Indicates that a brand is widely liked, recognized, or frequently chosen by many people.
-
D.
usedBrandOf
Indicates that one entity made use of or operated an item, product, or service associated with a particular brand.
-
E.
parentBrand
Indicates that one brand is the overarching or owning brand from which another brand is derived or subordinated.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eff1c18819081dc9dfc1816f746 |
completed | April 29, 2026, 3:46 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
Created at: April 17, 2026, 3:38 p.m.