Triple
T6253531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Astley family |
E140103
|
entity |
| Predicate | hasSurname |
P18
|
FINISHED |
| Object | Astley |
E290982
|
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: Astley | Statement: [Astley family, hasSurname, Astley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Astley Context triple: [Astley family, hasSurname, Astley]
-
A.
Astley
chosen
Astley is a village in Greater Manchester, England, known historically for its coal mining and rural character within the Leigh area.
-
B.
Astley Park
Astley Park is a historic public park in Chorley, Lancashire, known for its landscaped grounds, woodland, and the Grade I listed Astley Hall.
-
C.
Anstey
Anstey is a large village and civil parish in Leicestershire, England, situated just northwest of Leicester and known historically for its hosiery and footwear industries.
-
D.
Lankershim
Lankershim is a surname most notably associated with Isaac Lankershim, a 19th-century landowner and developer influential in the early growth of the Los Angeles area.
-
E.
Billingham
Billingham is an industrial town in County Durham, England, known historically for its chemical industry and proximity to the River Tees.
- 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_69c008b4858c819095b0199114a9a87b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063625608819081f5422112c80ce5 |
completed | March 22, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2442a556081908b91e7d999a82514 |
completed | March 24, 2026, 7:58 a.m. |
Created at: March 22, 2026, 4:24 p.m.