Triple
T15881317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilson Lumpkin |
E385080
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lumpkin |
E429290
|
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: Lumpkin | Statement: [Wilson Lumpkin, familyName, Lumpkin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lumpkin Context triple: [Wilson Lumpkin, familyName, Lumpkin]
-
A.
Lumpkin
chosen
Lumpkin is a surname of English origin borne by various notable individuals and families.
-
B.
Lowndes
Lowndes is a surname most prominently associated with Australian racing driver Craig Lowndes.
-
C.
Troup
Troup is a surname of Scottish origin borne by various notable individuals, including politicians, artists, and public figures.
-
D.
Lumpkin County
Lumpkin County is a county in northern Georgia known historically as a center of the Georgia Gold Rush and for its location in the Appalachian foothills.
-
E.
Fannin
Fannin is a surname of Scottish and Irish origin borne by various notable individuals, including historical and public figures.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156160a208190b30da2426411ee98 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffa95466e08190a967114821651e60 |
completed | May 9, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:51 a.m.