Triple
T3380750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xerox |
E71175
|
entity |
| Predicate | brandGenericization |
P47109
|
FINISHED |
| Object | photocopying |
—
|
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: photocopying | Statement: [Xerox, brandGenericization, photocopying]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brandGenericization Context triple: [Xerox, brandGenericization, photocopying]
-
A.
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.
-
B.
brandUsage
Indicates that one entity uses, features, or is associated with another entity’s brand in its products, services, or communications.
-
C.
brandRevival
Indicates the process or action of restoring a declining or dormant brand to renewed strength, relevance, and market presence.
-
D.
trademark
Indicates that one entity legally owns and uses a distinctive sign, name, or symbol to identify and distinguish its goods or services from those of others.
-
E.
formerBrand
Indicates that an entity was previously used or recognized as a brand for another entity but is no longer its current brand.
- F. None of above. chosen
Provenance (4 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_69ad85a7f80c8190a05e43013f298942 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb5e7c7f48190afb78c311b424c93 |
completed | March 8, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_69ada434bae48190a77ea37f9274ad8f |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada527ff308190813a7ffdcdec4322 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:14 p.m.