Triple
T28649931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Kelmscott Chaucer |
E725160
|
entity |
| Predicate | bordersDesigner |
P193653
|
FINISHED |
| Object | William Morris |
—
|
NE NERFINISHED |
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: William Morris | Statement: [The Kelmscott Chaucer, bordersDesigner, William Morris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersDesigner Context triple: [The Kelmscott Chaucer, bordersDesigner, William Morris]
-
A.
bordersEntity
Indicates that one entity shares a common boundary or border with another entity.
-
B.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
C.
bordersDefinedIn
Indicates that the boundaries or borders of one entity are specified, established, or formally described within another entity (such as a document, dataset, or legal instrument).
-
D.
connectsCountryBorder
Indicates that one entity forms a direct land or maritime border connection with a specified country.
-
E.
countryBorderFunction
Indicates that one country shares a land or maritime boundary with another country.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69fd4f38728c8190b3271abc80882cfb |
completed | May 8, 2026, 2:49 a.m. |
Created at: April 28, 2026, 4:51 a.m.