Triple
T14826694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenkinson family |
E348593
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Jenkinson |
E345715
|
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: Jenkinson | Statement: [Jenkinson family, hasFamilyName, Jenkinson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jenkinson Context triple: [Jenkinson family, hasFamilyName, Jenkinson]
-
A.
Jenkinson
chosen
Jenkinson is an English surname historically associated with notable political figures, including British prime ministers.
-
B.
Jenkynson
Jenkynson is a variant spelling of the surname Jenkinson, an English patronymic name meaning "son of Jenkin."
-
C.
Jenkens
Jenkens is an alternative spelling or variant form of the name Jenkins, which is commonly used as an English surname and given name.
-
D.
Jenkin
Jenkin is a variant form of the name Jenkins, typically used as a given name or surname of English and Welsh origin.
-
E.
Jenyns
Jenyns is an English surname historically associated with naturalist Leonard Jenyns and other notable figures in Britain.
- 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_69d822eb8f588190bf53445e730a934f |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded0713700819097bbb0352650984b |
completed | April 14, 2026, 11:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe389f48cc819089d860f0208dd465 |
completed | May 8, 2026, 7:25 p.m. |
Created at: April 10, 2026, 1:51 a.m.