Triple
T31397268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Electric model kitchen |
E800895
|
entity |
| Predicate | applianceCategory |
P95272
|
FINISHED |
| Object | kitchen appliances |
—
|
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: kitchen appliances | Statement: [General Electric model kitchen, applianceCategory, kitchen appliances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applianceCategory Context triple: [General Electric model kitchen, applianceCategory, kitchen appliances]
-
A.
cookingAppliance
Indicates that one entity is an appliance used by another entity for cooking food.
-
B.
hardwareCategory
Indicates that an item belongs to or is classified under a specific hardware category or type.
-
C.
domesticRange
Indicates the typical geographic or environmental area within which an entity normally lives, operates, or is found in its native or home context.
-
D.
onsenCategory
Indicates that one entity is classified as belonging to a particular category or type within the context of hot springs (onsen).
-
E.
commonUseCategory
chosen
Indicates that multiple entities share the same general category of use or functional purpose.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 29, 2026, 9:19 p.m.