Triple
T33674494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Worshipful Company of Cutlers |
E862720
|
entity |
| Predicate | typeOfEdgedToolsHistoricallyTraded |
P53121
|
FINISHED |
| Object | knives |
—
|
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: knives | Statement: [Worshipful Company of Cutlers, typeOfEdgedToolsHistoricallyTraded, knives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfEdgedToolsHistoricallyTraded Context triple: [Worshipful Company of Cutlers, typeOfEdgedToolsHistoricallyTraded, knives]
-
A.
weaponForgedFor
Indicates that a weapon was specifically created or crafted for a particular entity, purpose, or context.
-
B.
isToolOf
Indicates that one entity functions as an instrument or means used by another entity to perform tasks or achieve goals.
-
C.
bladeType
chosen
Indicates the specific kind or category of blade associated with an object or entity.
-
D.
bladeEdgeType
Indicates the specific form or style of the cutting edge present on a blade.
-
E.
bladeEdge
Indicates that one entity is the cutting edge or sharpened boundary of a blade-related object in relation to another entity.
- 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_69f34985885c8190914322f492e04703 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a00c486d394819084fe93d5bb11ea1e |
completed | May 10, 2026, 5:46 p.m. |
| PD | Predicate disambiguation | batch_6a00c39d99d48190a94bfa057213499c |
completed | May 10, 2026, 5:42 p.m. |
Created at: May 1, 2026, 1:43 a.m.