Triple
T19889335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Dickson (Tennessee politician) |
E477986
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Dickson |
E109715
|
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: Dickson | Statement: [William Dickson (Tennessee politician), familyName, Dickson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Dickson Context triple: [William Dickson (Tennessee politician), familyName, Dickson]
-
A.
Dickson
chosen
Dickson is a Scottish surname borne by various notable individuals across fields such as music, literature, and public life.
-
B.
Dickison
Dickison is a surname that functions as a spelling variant of the more common name Dickinson.
-
C.
Dirkson
Dirkson is a surname and given name variant most likely derived from the name Dirksen, commonly found in Germanic and Dutch-speaking regions.
-
D.
Dixon
Dixon is a small agricultural city in Northern California known historically for sheep ranching and its annual May Fair.
-
E.
Dixon
Dixon is an alternative name for Dikson, a remote Arctic settlement and port in northern Russia.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590ce9f48190a51c0e5ecc828a06 |
completed | April 20, 2026, 4:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07dbd3ac148190ba0067cacdf0f5d2 |
completed | May 16, 2026, 2:52 a.m. |
Created at: April 10, 2026, 1:52 p.m.