Triple
T8608413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Butler |
E203860
|
entity |
| Predicate | father |
P120
|
FINISHED |
| Object | Walter Butler |
E752805
|
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: Walter Butler | Statement: [John Butler, father, Walter Butler]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walter Butler Context triple: [John Butler, father, Walter Butler]
-
A.
Walter Butler
chosen
Walter Butler was a Loyalist military officer during the American Revolutionary War, notorious for leading brutal frontier raids against American settlements.
-
B.
Walter Lamb
Walter Lamb is a notable individual whose surname, Lamb, is recognized in records of prominent bearers of the name.
-
C.
Walter Baker
Walter Baker is a notable individual whose name is associated with various historical and professional contexts, including business and public service.
-
D.
Walter Hamilton
Walter Hamilton is a relatively obscure individual whose primary distinction is sharing the surname associated with the more widely known Hamilton family name.
-
E.
Walter Buckley
Walter Buckley is a notable individual recognized for achievements significant enough to be associated with the Buckley name.
- 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_69ca832c23e4819095a9f3eea4a21828 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46ec301881908ce148a3f07069fe |
completed | March 31, 2026, 10:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf5148add48190bd2849d607e46c77 |
completed | April 3, 2026, 5:34 a.m. |
Created at: March 30, 2026, 6:25 p.m.