Triple
T17975113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Haden Badley |
E449449
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Badley |
—
|
NE NERFINISHED |
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: Badley | Statement: [John Haden Badley, familyName, Badley]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Badley Context triple: [John Haden Badley, familyName, Badley]
-
A.
Badley
chosen
Badley is a small rural village and civil parish located in the English county of Suffolk.
-
B.
Daudley
Daudley is a surname variant historically associated with the English Audley family.
-
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.
Bransdale
Bransdale is a remote, steep-sided valley in the North York Moors of England, characterized by its pastoral landscapes and traditional farming.
-
E.
Blackley
Blackley is a suburban area of Manchester, England, known for its residential neighborhoods and proximity to the River Irk and local green spaces.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b1fee86c8190a9a220b008e78e10 |
completed | April 19, 2026, 10:44 a.m. |
Created at: April 10, 2026, 10:22 a.m.