Triple
T25703783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pope–Theobald controversy |
E644532
|
entity |
| Predicate | hasWorkAsKeyText |
P6200
|
FINISHED |
| Object | The Dunciad |
—
|
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: The Dunciad | Statement: [Pope–Theobald controversy, hasWorkAsKeyText, The Dunciad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkAsKeyText Context triple: [Pope–Theobald controversy, hasWorkAsKeyText, The Dunciad]
-
A.
hasKeyWork
chosen
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
B.
hasWorkBy
Indicates that one entity (such as a collection, exhibition, or publication) includes or contains creative works produced by another entity (such as an artist, author, or creator).
-
C.
hasWorkField
Indicates that an entity is associated with or operates within a particular field or area of work.
-
D.
hasWorkAsSubject
Indicates that an entity serves as the subject (creator or originator) of a particular work or creative output.
-
E.
hasWorkPart
Indicates that one work is a component, section, or constituent part of another, larger work.
- 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_69e77e83c8ec8190bf52fcdac4838984 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 21, 2026, 9 p.m.