Triple
T8278853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christian Heurich |
E193613
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Heurich |
E193613
|
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: Heurich | Statement: [Christian Heurich, familyName, Heurich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Heurich Context triple: [Christian Heurich, familyName, Heurich]
-
A.
Heurich
chosen
Heurich is a German surname most notably associated with Christian Heurich, a prominent brewer and businessman in Washington, D.C.
-
B.
Biesenthal
Biesenthal is a small town in the Barnim district of Brandenburg, Germany, known for its surrounding lakes, forests, and location within the Barnim Nature Park.
-
C.
Braunshardt
Braunshardt is a district of the town of Weiterstadt in the state of Hesse, Germany.
-
D.
Löwenthal
Löwenthal is the maiden surname of Elsa Einstein, who was both the second wife and cousin of physicist Albert Einstein.
-
E.
Hohberg
Hohberg is a municipality in the Ortenau district of Baden-Württemberg in southwestern Germany.
- 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_69ca82e217a48190880695635c44b2ed |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb79ebb6b88190bc777b8bd72fcdbc |
completed | March 31, 2026, 7:38 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd6863c22c8190b888a23bb9005712 |
completed | April 1, 2026, 6:48 p.m. |
Created at: March 30, 2026, 5:51 p.m.