Triple
T18208241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurd v. Hodge |
E435960
|
entity |
| Predicate | party |
P1790
|
FINISHED |
| Object | Hodge |
—
|
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: Hodge | Statement: [Hurd v. Hodge, party, Hodge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hodge Context triple: [Hurd v. Hodge, party, Hodge]
-
A.
Hodge
chosen
Hodge is a surname most notably associated with Charles Hodge, a prominent 19th-century American Presbyterian theologian.
-
B.
Hodges
Hodges is a surname most famously associated with Gil Hodges, the American Major League Baseball first baseman and manager.
-
C.
Hod
Hod is the eighth sephirah in the Kabbalistic Tree of Life, associated with intellect, communication, and the analytical aspect of divine energy.
-
D.
Hassler
Hassler Whitney was an influential American mathematician known for his foundational work in differential topology and manifold theory.
-
E.
Hood
Hood is an English surname historically associated with notable figures such as the British naval commander Samuel Hood, 1st Viscount Hood.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2261a848190b62a8485009f8f38 |
completed | April 19, 2026, 2:09 p.m. |
Created at: April 10, 2026, 10:32 a.m.