Triple
T22862883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Hartman |
E566970
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hartman |
—
|
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: Hartman | Statement: [Jack Hartman, familyName, Hartman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hartman Context triple: [Jack Hartman, familyName, Hartman]
-
A.
Hartman
chosen
Hartman is a surname of Germanic origin borne by various notable individuals across fields such as entertainment, academia, and politics.
-
B.
Hartmann
Hartmann is a German surname borne by numerous notable individuals across fields such as music, philosophy, and aviation.
-
C.
Harnell
Harnell is a surname most notably associated with American voice actor and singer Jess Harnell.
-
D.
Hesseman
Hesseman is a surname most notably associated with American actor and comedian Howard Hesseman, known for his role on the television series "WKRP in Cincinnati."
-
E.
Pittman
Pittman is a surname of English origin borne by various notable individuals across politics, sports, and the arts.
- 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_69e24589083081908d5694c4fdc80086 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17efdc3b08190be03d856aa86b277 |
completed | April 29, 2026, 3:46 a.m. |
Created at: April 17, 2026, 3:38 p.m.