Triple
T24845383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakai knives |
E621730
|
entity |
| Predicate | bladeEdgeType |
P157758
|
FINISHED |
| Object | double-bevel edge |
—
|
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: double-bevel edge | Statement: [Sakai knives, bladeEdgeType, double-bevel edge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bladeEdgeType Context triple: [Sakai knives, bladeEdgeType, double-bevel edge]
-
A.
bladeEdge
Indicates that one entity is the cutting edge or sharpened boundary of a blade-related object in relation to another entity.
-
B.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
C.
bladeDetail
Indicates that there is specific descriptive information or characteristics associated with a blade.
-
D.
sharpeningType
Indicates the method or style by which something is sharpened or made sharper.
-
E.
bladeConfiguration
Indicates how the blades in a system are arranged, structured, or set up relative to one another.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
| PDg | Predicate description generation | batch_69f44a3adb7c8190941572f718b3b93c |
completed | May 1, 2026, 6:37 a.m. |
Created at: April 18, 2026, 5:19 a.m.