Triple
T26252446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | three seaxes emblem of Essex |
E656628
|
entity |
| Predicate | bladeFeature |
P157758
|
FINISHED |
| Object | notched blades |
—
|
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: notched blades | Statement: [three seaxes emblem of Essex, bladeFeature, notched blades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bladeFeature Context triple: [three seaxes emblem of Essex, bladeFeature, notched blades]
-
A.
bladeDetail
Indicates that there is specific descriptive information or characteristics associated with a blade.
-
B.
bladeType
Indicates the specific kind or category of blade associated with an object or entity.
-
C.
bladeConfiguration
Indicates how the blades in a system are arranged, structured, or set up relative to one another.
-
D.
bladeEdge
Indicates that one entity is the cutting edge or sharpened boundary of a blade-related object in relation to another entity.
-
E.
bladeEdgeType
chosen
Indicates the specific form or style of the cutting edge present on a blade.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcb59cc819095eda1b1a4947a19 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 9:07 p.m.