Triple
T6274146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenkins |
E140612
|
entity |
| Predicate | hasCognate |
P2525
|
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: [Jenkins, hasCognate, Jenkinson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jenkinson Context triple: [Jenkins, hasCognate, Jenkinson]
-
A.
Jenkinson
chosen
Jenkinson is an English surname historically associated with notable political figures, including British prime ministers.
-
B.
Wilkinson
Wilkinson is an English surname, originally a patronymic meaning "son of Wilkin," that has been borne by various notable figures and brands.
-
C.
Johnsen
Johnsen is a surname of Scandinavian origin, commonly used as a patronymic family name meaning "son of John."
-
D.
Jurgensen
Jurgensen is the surname of Sonny Jurgensen, a Hall of Fame American football quarterback best known for his prolific passing career with the Washington Redskins.
-
E.
Jenssen
Jenssen is a Scandinavian surname, particularly common in Norway, that originated as a patronymic form meaning "son of Jens."
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063c0629c8190805ddf1a604e9ca4 |
completed | March 22, 2026, 9:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c2446ad060819094acd817ba5eadc9 |
completed | March 24, 2026, 7:59 a.m. |
Created at: March 22, 2026, 4:25 p.m.