Triple
T22667379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard T. Whitcomb |
E559826
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Whitcomb |
—
|
NE NERFINISHED |
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: Whitcomb | Statement: [Richard T. Whitcomb, familyName, Whitcomb]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Whitcomb Context triple: [Richard T. Whitcomb, familyName, Whitcomb]
-
A.
Whitcomb
chosen
Whitcomb is the middle name of James Whitcomb Riley, the renowned American poet known as the "Hoosier Poet" for his dialect verse and children's poetry.
-
B.
Whitmore
Whitmore is an English surname historically associated with several notable families and individuals in Britain.
-
C.
Tugwell
Tugwell is a surname most notably associated with Rexford G. Tugwell, an American economist and member of President Franklin D. Roosevelt’s New Deal "Brain Trust."
-
D.
Whitmire
Whitmire is a given name associated with David Whitmire Hearst, a member of the Hearst family.
-
E.
Foraker
Foraker is a surname most notably associated with Joseph B. Foraker, a prominent American politician who served as governor of Ohio and U.S. senator in the late 19th and early 20th centuries.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1781ceca08190ba1309570e81c5af |
completed | April 29, 2026, 3:16 a.m. |
Created at: April 17, 2026, 3:09 p.m.