Triple
T14217058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keeley Hawes |
E352380
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hawes |
E295794
|
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: Hawes | Statement: [Keeley Hawes, familyName, Hawes]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hawes Context triple: [Keeley Hawes, familyName, Hawes]
-
A.
Hawes
chosen
Hawes is a small market town in North Yorkshire, England, known for its scenic location in Wensleydale and its traditional cheese-making heritage.
-
B.
Hawkinson
Hawkinson is a surname of likely English origin, derived as a variant of the name Hawkins.
-
C.
Hawkwell
Hawkwell is a village and civil parish in the Rochford District of Essex, England, known for its residential character and proximity to the town of Rochford.
-
D.
Hawise
Hawise is a medieval European female given name borne by several noblewomen in England and France.
-
E.
Upshaw
Upshaw is a surname most notably associated with several prominent American figures in sports, politics, and civil rights.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6210213481908fac6893e8a9f143 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd28101e1881909f7a6c0cc762204c |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:06 a.m.