Triple
T33661025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden Treasury |
E862350
|
entity |
| Predicate | includedPoets |
P152712
|
FINISHED |
| Object | William Shakespeare |
E20950
|
NE 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: William Shakespeare | Statement: [The Golden Treasury, includedPoets, William Shakespeare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPoets Context triple: [The Golden Treasury, includedPoets, William Shakespeare]
-
A.
includesPoetsFrom
Indicates that one entity contains, features, or is composed of poets originating from another entity.
-
B.
containsPoemsFrom
Indicates that one entity includes or features poems that originate from or are authored in association with another entity.
-
C.
featuredPoet
Indicates that a person is highlighted or showcased as a poet in a special or prominent context.
-
D.
favoritePoet
Indicates that one entity is the poet whom another entity prefers above all other poets.
-
E.
poetAssociated
chosen
Indicates a relationship where a poet is connected or linked to another entity, such as a work, place, movement, or person, through relevance, collaboration, influence, or affiliation.
- F. None of above.
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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a033ed9322c8190be994a8d99761caa |
completed | May 12, 2026, 2:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a362721daac819081449daf7b0b2863 |
completed | June 20, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a033df2b254819082a672859e5168e6 |
completed | May 12, 2026, 2:49 p.m. |
Created at: May 1, 2026, 1:42 a.m.