Triple
T12426986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah Emmerich |
E296923
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Emmerich |
E879302
|
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: Emmerich | Statement: [Noah Emmerich, familyName, Emmerich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Emmerich Context triple: [Noah Emmerich, familyName, Emmerich]
-
A.
Emmerich
chosen
Emmerich is the German form of the given name Imre, used primarily in German-speaking regions.
-
B.
Veit
Veit is a German surname most notably associated with the 19th-century Romantic painter Philipp Veit.
-
C.
Reimund
Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
-
D.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
E.
Othmar
Othmar is a masculine given name of Germanic origin, notably borne by the Swiss-American civil engineer Othmar Ammann.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94d7ccda08190be2ff1739c1c6855 |
completed | April 10, 2026, 7:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f63499061881908d25af7c3474f774 |
completed | May 2, 2026, 5:30 p.m. |
Created at: April 8, 2026, 9:55 p.m.