Triple
T23333286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Cavendish of Hardwick |
E591503
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | Hardwick |
—
|
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: Hardwick | Statement: [Baron Cavendish of Hardwick, namedAfter, Hardwick]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hardwick Context triple: [Baron Cavendish of Hardwick, namedAfter, Hardwick]
-
A.
Hardwick
Hardwick is a village and civil parish in the South Cambridgeshire district of Cambridgeshire, England.
-
B.
Hardwick
chosen
Hardwick is an English country estate in Derbyshire best known for its grand Elizabethan mansion, Hardwick Hall, historically associated with the Cavendish family.
-
C.
Hardwick
Hardwick is an English-origin surname borne by various notable individuals across fields such as sports, politics, and the arts.
-
D.
Hardwick
Hardwick is a small rural town in Vermont known for its agricultural heritage and location within the scenic Northeast Kingdom region.
-
E.
Hardwick
Hardwick is a small settlement in Oxfordshire, England, forming part of the civil parish of Ducklington.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e25d20156c81908c5c53195bd9c738 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f197efd98c819083635a2b8440f3eb |
completed | April 29, 2026, 5:32 a.m. |
Created at: April 17, 2026, 5:16 p.m.