Triple
T7136217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rape of the Lock |
E166312
|
entity |
| Predicate | expandedEditionPublicationDate |
P16584
|
FINISHED |
| Object | 1714 |
—
|
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: 1714 | Statement: [The Rape of the Lock, expandedEditionPublicationDate, 1714]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandedEditionPublicationDate Context triple: [The Rape of the Lock, expandedEditionPublicationDate, 1714]
-
A.
expandedEditionYear
chosen
Indicates the year in which a work’s expanded or enlarged edition was published or released.
-
B.
expandedEditionIncludes
Indicates that an expanded edition of a work contains, as part of its content, the material from another specified edition or version.
-
C.
anniversaryEditionPublicationYear
Indicates the year in which an anniversary edition of a work was published.
-
D.
strengthenedEditionYear
Indicates the year in which a particular edition was revised or enhanced to become a strengthened version.
-
E.
expansionReleaseDate
Indicates the date on which an expansion (such as an add-on or supplementary release) is officially made available.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e6926d748190bc8c150fc1860531 |
completed | March 27, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:45 p.m.