Triple
T14210867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Viscounts Mersey |
E352226
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bigham |
E352226
|
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: Bigham | Statement: [Viscounts Mersey, familyName, Bigham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bigham Context triple: [Viscounts Mersey, familyName, Bigham]
-
A.
Bigham
chosen
Bigham is an English surname historically associated with British nobility, including the Viscounts Mersey.
-
B.
Bingam
Bingam is a variant form of the name Bingham, which is used as both a surname and a place name in English-speaking regions.
-
C.
Brimley
Brimley is a surname most notably associated with American actor Wilford Brimley, known for his roles in film, television, and commercials.
-
D.
Burgin
Burgin is a small rural city in Mercer County, Kentucky, known for its tight-knit community and location near Herrington Lake.
-
E.
Whigham
Whigham is a surname most notably associated with American actor Shea Whigham, known for his character roles in film and television.
- 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_69de620dba0c8190bb77a1df10e1d3a7 |
completed | April 14, 2026, 3:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd19574280819091bafd95a75983bf |
completed | May 7, 2026, 10:59 p.m. |
Created at: April 10, 2026, 1:05 a.m.