Triple
T8326106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kelmscott Press |
E194957
|
entity |
| Predicate | bindingStyle |
P82116
|
FINISHED |
| Object | decorative leather bindings |
—
|
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: decorative leather bindings | Statement: [Kelmscott Press, bindingStyle, decorative leather bindings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingStyle Context triple: [Kelmscott Press, bindingStyle, decorative leather bindings]
-
A.
bindingOption
Indicates a relationship where one entity specifies or constrains how another entity is bound, attached, or associated within a given context or configuration.
-
B.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
C.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
D.
passingStyle
Indicates the manner or technique by which something (typically a ball or object) is passed from one entity to another.
-
E.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f7fba688190b696593dfb2cde5d |
completed | March 31, 2026, 8:02 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:56 p.m.