Triple
T28649880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Works of Geoffrey Chaucer |
E725159
|
entity |
| Predicate | hasBordersBy |
P181657
|
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 Works of Geoffrey Chaucer, hasBordersBy, William Morris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBordersBy Context triple: [The Works of Geoffrey Chaucer, hasBordersBy, William Morris]
-
A.
hadBorderType
Indicates that a boundary between two entities existed and specifies the nature or classification of that border (e.g., land, maritime, disputed).
-
B.
hasBorderThrough
Indicates that a border between two regions or entities passes through or along a specified intermediate area, feature, or object.
-
C.
hasBorderCode
Indicates that there is an associated code or identifier specifying the type or status of a border between entities.
-
D.
hasBorderRelation
Indicates that one entity shares a boundary or border with another entity.
-
E.
hasBorderElement
Indicates that one entity includes or is associated with another entity that forms part of its boundary or edge.
- 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_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
| PDg | Predicate description generation | batch_69f7805c25dc8190b9977c561ba15975 |
completed | May 3, 2026, 5:05 p.m. |
Created at: April 28, 2026, 4:51 a.m.