Triple
T10875963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomas Walpole |
E256798
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Walpole |
E193948
|
NE 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: Walpole | Statement: [Thomas Walpole, familyName, Walpole]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walpole Context triple: [Thomas Walpole, familyName, Walpole]
-
A.
Walpole
chosen
Walpole is a prominent English surname most famously associated with the 18th-century statesman Robert Walpole, often regarded as Britain’s first de facto Prime Minister.
-
B.
Walpole, Suffolk
Walpole, Suffolk is a small rural village and civil parish in the county of Suffolk, England.
-
C.
Walpole, Norfolk
Walpole, Norfolk is a small rural village and civil parish in the county of Norfolk, England, known for its agricultural landscape and historic parish churches.
-
D.
Grenville
Grenville was a former county-level jurisdiction in Ontario, Canada, that later became part of the combined Leeds and Grenville administrative region.
-
E.
Grenville
Grenville is a masculine given name most notably borne by American Civil War general and railroad engineer Grenville M. Dodge.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d751ac901881909938cabe4d21bdbf |
completed | April 9, 2026, 7:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69dff7ddafc48190824c133bb33b9efe |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 8, 2026, 9:21 p.m.