Triple
T10016931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doak Walker |
E199518
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Walker |
E186941
|
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: Walker | Statement: [Doak Walker, familyName, Walker]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Walker Context triple: [Doak Walker, familyName, Walker]
-
A.
Walker
Walker is a small city located in Vernon County in the western part of the U.S. state of Missouri.
-
B.
Walker
chosen
Walker is a common English surname borne by numerous notable individuals across fields such as politics, sports, the arts, and civil rights leadership.
-
C.
Blake
Blake is a given name and surname used in English-speaking countries for people of any gender.
-
D.
Jack
Jack is the standard botanical author abbreviation for William Jack, a 19th-century Scottish physician and botanist known for his work on Southeast Asian flora.
-
E.
Jack
Jack is a common masculine given name, often used as a familiar form of John and widely featured in English-language literature and popular culture.
- 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_69ca8315a1a08190ab310f25620f362b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd4c17848190bf1a8017e755ba75 |
completed | April 2, 2026, 1:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26aa319508190b85b5a5f78603b6a |
completed | April 5, 2026, 1:58 p.m. |
Created at: March 30, 2026, 8:53 p.m.