Triple
T14819204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shari Headley |
E348399
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Headley
Headley is a surname of English origin borne by various notable individuals across fields such as entertainment, sports, and politics.
|
E1121585
|
NE FINISHED |
How this triple was built (4 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: Headley | Statement: [Shari Headley, familyName, Headley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Headley Context triple: [Shari Headley, familyName, Headley]
-
A.
Headley
Headley is a village in Surrey, England, known for its rural character and location within the North Downs.
-
B.
Headley
Headley is a village and civil parish in the East Hampshire district of Hampshire, England, known for its rural character and historic parish church.
-
C.
Edgeley
Edgeley is a suburban area in Stockport, Greater Manchester, historically part of Cheshire, known for its residential character and proximity to Stockport town centre.
-
D.
Lumley
Lumley is an English surname historically associated with a prominent aristocratic family, including holders of titles such as Viscount and Earl in the British peerage.
-
E.
Midgley
Midgley is a small village in West Yorkshire, England, known for its rural setting in the Calder Valley near Luddenden Foot.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Headley Triple: [Shari Headley, familyName, Headley]
Generated description
Headley is a surname of English origin borne by various notable individuals across fields such as entertainment, sports, and politics.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Headley Target entity description: Headley is a surname of English origin borne by various notable individuals across fields such as entertainment, sports, and politics.
-
A.
Headley
Headley is a village in Surrey, England, known for its rural character and location within the North Downs.
-
B.
Headley
Headley is a village and civil parish in the East Hampshire district of Hampshire, England, known for its rural character and historic parish church.
-
C.
Edgeley
Edgeley is a suburban area in Stockport, Greater Manchester, historically part of Cheshire, known for its residential character and proximity to Stockport town centre.
-
D.
Lumley
Lumley is an English surname historically associated with a prominent aristocratic family, including holders of titles such as Viscount and Earl in the British peerage.
-
E.
Midgley
Midgley is a small village in West Yorkshire, England, known for its rural setting in the Calder Valley near Luddenden Foot.
- F. None of above. chosen
Provenance (5 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decfe4cf38819090f25ef045351d5d |
completed | April 14, 2026, 11:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389940e081908ad627955cb8d52e |
completed | May 8, 2026, 7:25 p.m. |
| NEDg | Description generation | batch_69fe3a315d2c81908db44e7792908e39 |
completed | May 8, 2026, 7:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe3bda81cc8190b256ec6284383dde |
completed | May 8, 2026, 7:39 p.m. |
Created at: April 10, 2026, 1:50 a.m.