Triple
T32808584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earls of Derwentwater |
E839082
|
entity |
| Predicate | thirdEarlExecutionPlace |
P24295
|
FINISHED |
| Object | Tower Hill, London |
—
|
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: Tower Hill, London | Statement: [Earls of Derwentwater, thirdEarlExecutionPlace, Tower Hill, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdEarlExecutionPlace Context triple: [Earls of Derwentwater, thirdEarlExecutionPlace, Tower Hill, London]
-
A.
placeOfExecution
chosen
Indicates the location where an execution or carrying out of a sentence, order, or legal punishment took place.
-
B.
outcomeForCharlesI
Indicates the resulting fate, consequence, or end state that befell Charles I as a result of preceding events or actions.
-
C.
notablePrisonerExecuted
Indicates that a person, recognized as a notable or significant prisoner, was executed while in custody.
-
D.
placeOfKilling
Indicates the location where a killing event took place.
-
E.
dateOfDefenestration
Indicates the specific date on which an entity was thrown out of a window (defenestrated).
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 1, 2026, 1:15 a.m.