Triple
T6671175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Baskerville |
E151732
|
entity |
| Predicate | birthplace |
P1
|
FINISHED |
| Object | Wolverley |
E151732
|
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: Wolverley | Statement: [John Baskerville, birthplace, Wolverley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wolverley Context triple: [John Baskerville, birthplace, Wolverley]
-
A.
Wolverley
chosen
Wolverley is a village in Worcestershire, England, known as the birthplace of the renowned 18th-century printer and typographer John Baskerville.
-
B.
Wrottesley
Wrottesley is an English surname historically associated with a prominent aristocratic family and the title Baron Wrottesley.
-
C.
Wolverton
Wolverton is a historic railway town in Buckinghamshire, England, now part of the Milton Keynes urban area.
-
D.
Rugeley
Rugeley is a market town in Staffordshire, England, historically known for its coal mining industry and location on the River Trent.
-
E.
Weobley
Weobley is a historic village and former parliamentary borough in Herefordshire, England, known for its timber-framed buildings and medieval origins.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6b0c9163c8190ad959172a8458619 |
completed | March 27, 2026, 4:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c700755874819083cd0facebd7aa3d |
completed | March 27, 2026, 10:11 p.m. |
Created at: March 27, 2026, 2:03 p.m.