Triple
T13024268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Nelson, 1st Earl Nelson |
E326259
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Edmund Nelson |
E65512
|
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: Edmund Nelson | Statement: [William Nelson, 1st Earl Nelson, father, Edmund Nelson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Edmund Nelson Context triple: [William Nelson, 1st Earl Nelson, father, Edmund Nelson]
-
A.
Edmund Nelson
chosen
Edmund Nelson was an 18th-century English clergyman best known as the father of Admiral Horatio Nelson.
-
B.
Edmund Nelson Jr.
Edmund Nelson Jr. is the son of former NFL defensive lineman Edmund Nelson.
-
C.
Edmund Pearce
Edmund Pearce was an Anglican clergyman who served as the Bishop of Derby in the Church of England.
-
D.
Edmund Joseph
Edmund Joseph was an American screenwriter active during Hollywood's classic studio era, contributing to several popular films of the mid-20th century.
-
E.
Edmund Osborne
Edmund Osborne was a senior British Army officer who commanded II Corps during the Second World War.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efac71881908a21d70c3c6ce099 |
completed | April 10, 2026, 10:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6c11c1f6c8190be1c570a7e44a313 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 9, 2026, 8:52 p.m.