Triple
T13254930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James Broughton |
E315632
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Broughton |
E645984
|
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: Broughton | Statement: [James Broughton, familyName, Broughton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Broughton Context triple: [James Broughton, familyName, Broughton]
-
A.
Broughton
Broughton is a small coastal settlement on the Gower Peninsula in Wales, known for its nearby beaches and rural surroundings.
-
B.
Broughton
Broughton is a small rural village in the Scottish Borders region of Scotland, historically part of the county of Peeblesshire.
-
C.
Broughton
chosen
Broughton is an English-language surname borne by various notable individuals across fields such as exploration, politics, sports, and the arts.
-
D.
Broughton
Broughton is a town in North Lincolnshire, England, historically associated with the former local government district of Glanford.
-
E.
Higher Broughton
Higher Broughton is a residential district in Salford, Greater Manchester, known for its diverse community and proximity to Manchester city centre.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98f7517048190b4eac4e44e81ff66 |
completed | April 11, 2026, 12:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f70a3d6b808190b4ae5225961de03f |
completed | May 3, 2026, 8:41 a.m. |
Created at: April 9, 2026, 9:24 p.m.