Triple
T23204375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenkin |
E580406
|
entity |
| Predicate | hasSpellingVariant |
P457
|
FINISHED |
| Object | Jenkyn |
—
|
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: Jenkyn | Statement: [Jenkin, hasSpellingVariant, Jenkyn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jenkyn Context triple: [Jenkin, hasSpellingVariant, Jenkyn]
-
A.
Jenkyn
chosen
Jenkyn is a less common variant spelling of the surname Jenkins, typically of Welsh or English origin.
-
B.
Jenyns
Jenyns is an English surname historically associated with naturalist Leonard Jenyns and other notable figures in Britain.
-
C.
Jenkin
Jenkin is a variant form of the name Jenkins, typically used as a given name or surname of English and Welsh origin.
-
D.
Savige
Savige is an English-language surname most notably associated with Australian Lieutenant General Sir Stanley Savige, a distinguished military leader and humanitarian.
-
E.
Graydon
Graydon is a surname of English and Irish origin borne by various notable individuals, including those in politics, sports, and the arts.
- 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_69e24602ae1481908aaa6bc7ca493867 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1907b3e88819088a397a99456bf77 |
completed | April 29, 2026, 5 a.m. |
Created at: April 17, 2026, 4:07 p.m.