Triple
T31374067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canon printer lineup |
E800241
|
entity |
| Predicate | includesConsumableType |
P203122
|
FINISHED |
| Object | ink cartridges |
—
|
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: ink cartridges | Statement: [Canon printer lineup, includesConsumableType, ink cartridges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesConsumableType Context triple: [Canon printer lineup, includesConsumableType, ink cartridges]
-
A.
canBeConsumedWith
Indicates that one entity is suitable or appropriate to be eaten, drunk, or otherwise consumed together with another entity.
-
B.
isTypicallyConsumedFrom
Indicates that one entity is most commonly eaten or drunk using, contained in, or taken from the other entity.
-
C.
isConsumedIn
Indicates that one entity is used up, ingested, or otherwise expended as part of a process, event, or action involving another entity.
-
D.
hasDishType
Indicates that an item (such as a food or menu entry) is classified as belonging to a particular type of dish (e.g., appetizer, main course, dessert).
-
E.
consumptionRestriction
Indicates a limitation or prohibition on the use or consumption of a specified resource, product, or item.
- 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_69f224e84da08190abfc2f17494a33c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a0124a5d7848190a6b56d18db2f661d |
completed | May 11, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_6a01243da1808190ada3ce553e3f55b6 |
completed | May 11, 2026, 12:35 a.m. |
| PDg | Predicate description generation | batch_6a0124a538a08190b42e6f35d216da74 |
completed | May 11, 2026, 12:36 a.m. |
Created at: April 29, 2026, 9:18 p.m.