Triple
T3424260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinz Ewald |
E72189
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Ewald |
E197452
|
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: Ewald | Statement: [Heinz Ewald, familyName, Ewald]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewald Context triple: [Heinz Ewald, familyName, Ewald]
-
A.
Ewald
chosen
Ewald is a masculine given name of Germanic origin, historically borne by various notable figures in German and Central European history.
-
B.
Hittorff
Hittorff is the surname of Jacques Ignace Hittorff, a prominent 19th-century German-born French architect known for his work on Parisian urban design and monuments.
-
C.
Rechenberg
Rechenberg is a locality in Germany known historically as the place where the philosopher Ludwig Feuerbach died.
-
D.
Eberl
Eberl is a German-language surname of Austrian and Bavarian origin borne by various notable individuals.
-
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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb9533b588190a18a9b6495712ee0 |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b3547468b8819088e7c4cf3b2e2079 |
completed | March 13, 2026, 12:04 a.m. |
Created at: March 8, 2026, 3:15 p.m.