Triple
T28649872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Works of Geoffrey Chaucer |
E725159
|
entity |
| Predicate | typeDesigner |
P128440
|
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, typeDesigner, William Morris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeDesigner Context triple: [The Works of Geoffrey Chaucer, typeDesigner, William Morris]
-
A.
designerType
Indicates the specific kind or category of designer role associated with an entity.
-
B.
type2ReverseDesigner
chosen
Indicates that an entity serves as the reverse or inverse designer of another entity, capturing a design relationship oriented in the opposite direction of a primary "designer" link.
-
C.
keyDesigner
Indicates that an entity serves as the primary or lead designer responsible for creating or shaping another entity.
-
D.
characterDesigner
Indicates a relationship where an entity is responsible for designing or creating the visual or conceptual characteristics of a character.
-
E.
featureDesigner
Indicates that a person serves as the designer responsible for creating or specifying a particular feature.
- 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_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:51 a.m.