Triple
T14717371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jenkinson |
E345715
|
entity |
| Predicate | derivedFromGivenName |
P17
|
FINISHED |
| Object | John |
unclear NED1
|
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: John | Statement: [Jenkinson, derivedFromGivenName, John]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: John Context triple: [Jenkinson, derivedFromGivenName, John]
-
A.
John
John is the husband of Martha Rainsborough.
-
B.
John
John is the given name of John Henry Patterson, an American industrialist and founder of the National Cash Register Company.
-
C.
John
John B. Magruder was a Confederate major general during the American Civil War, known for his leadership in the Peninsula Campaign and his flamboyant personality.
-
D.
John
John is the given name of John Howard, an Australian politician who served as the 25th Prime Minister of Australia.
-
E.
John
John is the given name of Sir John Woodville, a 15th-century English nobleman associated with the influential Woodville family during the Wars of the Roses.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d822e5911c8190ba589f957dbd9ba7 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb98688f48190b2b19ce7aa06a6db |
completed | April 14, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fdf07c7fa88190bb09f2f444d69786 |
completed | May 8, 2026, 2:17 p.m. |
Created at: April 10, 2026, 1:29 a.m.