Triple
T13594186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 30 bayonet |
E324771
|
entity |
| Predicate | scabbardMaterial |
P110211
|
FINISHED |
| Object | metal scabbard |
—
|
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: metal scabbard | Statement: [Type 30 bayonet, scabbardMaterial, metal scabbard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scabbardMaterial Context triple: [Type 30 bayonet, scabbardMaterial, metal scabbard]
-
A.
hasScabbard
Indicates that an item, typically a bladed weapon, is accompanied by or stored in a scabbard designed to hold it.
-
B.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
C.
bladeEdge
Indicates that one entity is the cutting edge or sharpened boundary of a blade-related object in relation to another entity.
-
D.
bladeDetail
Indicates that there is specific descriptive information or characteristics associated with a blade.
-
E.
ancestralSwordMaterial
Indicates that an ancestral sword is made from a specified material.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb057f1c881909a3bb77c659a724a |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbaf9f3bdc8190838539aaef1f422b |
completed | April 12, 2026, 2:43 p.m. |
Created at: April 9, 2026, 9:49 p.m.