Triple
T22750985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James K. Hahn |
E562695
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Hahn |
—
|
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: Hahn | Statement: [James K. Hahn, familyName, Hahn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hahn Context triple: [James K. Hahn, familyName, Hahn]
-
A.
Hahn
chosen
Hahn is a surname of German origin borne by various notable individuals across fields such as science, sports, and the arts.
-
B.
Fahrenkopf
Fahrenkopf is a surname most prominently associated with Frank J. Fahrenkopf Jr., an American lawyer, lobbyist, and former chairman of the Republican National Committee.
-
C.
Haan
Haan is a town in the German state of North Rhine-Westphalia, known for its location between Düsseldorf and Wuppertal and its mix of residential areas and light industry.
-
D.
Haan
Haan is a music producer and member of the hip-hop and trap-focused collective Internet Money.
-
E.
Hachen
Hachen is a district (Ortsteil) of the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179b9ac348190bff4dc470931f7e3 |
completed | April 29, 2026, 3:23 a.m. |
Created at: April 17, 2026, 3:24 p.m.