Triple
T28649989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Story of the Glittering Plain |
E725161
|
entity |
| Predicate | hasPageDesign |
P1529
|
FINISHED |
| Object | ornamental borders in Kelmscott Press edition |
—
|
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: ornamental borders in Kelmscott Press edition | Statement: [The Story of the Glittering Plain, hasPageDesign, ornamental borders in Kelmscott Press edition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPageDesign Context triple: [The Story of the Glittering Plain, hasPageDesign, ornamental borders in Kelmscott Press edition]
-
A.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
C.
hasDesigned
Indicates that one entity is the creator or designer of another entity.
-
D.
hasDesignPhase
Indicates that an entity is associated with or undergoes a specific design phase within a broader process or lifecycle.
-
E.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
- 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_69f01d8423888190bd2f4e52605bf261 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 28, 2026, 4:51 a.m.