Triple
T10283110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gil Hodges |
E241153
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hodges |
E182770
|
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: Hodges | Statement: [Gil Hodges, familyName, Hodges]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hodges Context triple: [Gil 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.
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.
-
C.
D. Hodges
D. Hodges is a music producer known for work on influential hip-hop recordings such as Mos Def’s album "Black on Both Sides."
-
D.
John Hodges
John Hodges is a film and television producer best known as a co-founder and former chief operating officer of the independent entertainment company A24.
-
E.
George Hodges
George Hodges is a relatively obscure individual whose name is notably recorded as a bearer of the surname Hodges.
- 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_69d381a94c1881908fc38fc263d9b9c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2a22f9881908b220dbe1e80c101 |
completed | April 7, 2026, 9:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d6f83c3c488190b728783bc260b006 |
completed | April 9, 2026, 12:52 a.m. |
Created at: April 6, 2026, 11:39 a.m.