Triple
T36978456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilot Kakuno |
E914758
|
entity |
| Predicate | compatibleInkCartridge |
P194968
|
FINISHED |
| Object | Pilot proprietary ink cartridge |
—
|
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: Pilot proprietary ink cartridge | Statement: [Pilot Kakuno, compatibleInkCartridge, Pilot proprietary ink cartridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compatibleInkCartridge Context triple: [Pilot Kakuno, compatibleInkCartridge, Pilot proprietary ink cartridge]
-
A.
cartridgeColor
Indicates that one entity is the color attribute associated with a particular cartridge.
-
B.
usesInk
Indicates that one entity operates or functions by employing ink as a necessary medium or material.
-
C.
featuresCartouchesOf
Indicates that something (such as an artifact, monument, or object) bears or includes cartouches that contain the names or titles of specific individuals or entities.
-
D.
haveInkColor
Indicates that an entity (such as a writing instrument or printer) possesses ink of a specified color.
-
E.
capacityComparedToCartridge
Indicates how the capacity of one item compares to that of a reference cartridge.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
| PDg | Predicate description generation | batch_69fd91a44268819081b372296e3aa116 |
completed | May 8, 2026, 7:32 a.m. |
Created at: May 3, 2026, 4:14 p.m.