Triple
T22406727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craig Hodges |
E553897
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hodges |
—
|
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: Hodges | Statement: [Craig Hodges, familyName, Hodges]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hodges Context triple: [Craig Hodges, familyName, Hodges]
-
A.
Hodges
chosen
Hodges is a surname most famously associated with Gil Hodges, the American Major League Baseball first baseman and manager.
-
B.
Hodges
Hodges is a small town located in Greenwood County in the state of South Carolina, United States.
-
C.
Hodges and Smith
Hodges and Smith was a 19th-century Dublin-based publishing firm known for issuing scholarly and mathematical works, including significant contributions to the development of modern algebra.
-
D.
Huggins
Huggins is a surname most prominently associated with Bob Huggins, a longtime American college basketball coach known for his successful and hard-nosed teams.
-
E.
Jack Hodges
Jack Hodges is a person notable enough to be recognized as a bearer of the surname Hodges, though specific widely known biographical details are not clearly established.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b835e88190a388e19577df771e |
completed | April 29, 2026, 1:02 a.m. |
Created at: April 16, 2026, 8:46 p.m.