Triple
T28649948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Kelmscott Chaucer |
E725160
|
entity |
| Predicate | bindingTypical |
P165531
|
FINISHED |
| Object | vellum over boards |
—
|
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: vellum over boards | Statement: [The Kelmscott Chaucer, bindingTypical, vellum over boards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bindingTypical Context triple: [The Kelmscott Chaucer, bindingTypical, vellum over boards]
-
A.
binding
Indicates that one entity physically or chemically attaches, adheres, or forms a stable association with another entity.
-
B.
bindingFor
Indicates that one entity serves as the binding, constraint, or linkage mechanism that determines how another entity is associated, applied, or made effective.
-
C.
typicalBonding
Indicates a usual or characteristic bonding relationship that commonly occurs between the involved entities.
-
D.
bindingAsTo
Indicates that one entity is legally or contractually binding upon another entity with respect to certain terms, obligations, or conditions.
-
E.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 4:51 a.m.