Triple
T25665994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton’s Cottage |
E643517
|
entity |
| Predicate | notableWorkCompletedHere |
P20732
|
FINISHED |
| Object | Paradise Lost |
—
|
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: Paradise Lost | Statement: [Milton’s Cottage, notableWorkCompletedHere, Paradise Lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWorkCompletedHere Context triple: [Milton’s Cottage, notableWorkCompletedHere, Paradise Lost]
-
A.
notableWorkPerformed
chosen
Indicates that an entity has created, executed, or contributed significantly to a particular work that is recognized as notable or important.
-
B.
notableWorkSetHere
Indicates that a notable creative work is set in or takes place within the referenced location.
-
C.
notablePlaceOfWork
Indicates that there is a notable or significant place where the entity has worked or been employed.
-
D.
notableWorkArea
Indicates the field or domain in which an entity’s significant work or contributions are primarily focused.
-
E.
notableWork
Indicates that one entity is a significant or well-known work (such as a book, artwork, or creation) produced by another entity.
- 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_69e77e7e45648190a068ed3faa8016ea |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 21, 2026, 7:04 p.m.