Triple
T4321428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hermann Einstein |
E96524
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Hermann |
E234352
|
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: Hermann | Statement: [Hermann Einstein, givenName, Hermann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hermann Context triple: [Hermann Einstein, givenName, Hermann]
-
A.
Hermann
chosen
Hermann is a German surname borne by various notable individuals across fields such as philosophy, science, and the arts.
-
B.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
C.
Günther
Günther is a German masculine given name traditionally associated with figures of Germanic origin and culture.
-
D.
Helmuth
Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
-
E.
Wilhelm
Wilhelm is a Germanic given name, equivalent to William, historically borne by numerous European nobles, rulers, and notable figures.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3511608dc8190afe912aa605ecace |
completed | March 12, 2026, 11:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bd6f7bfd4c8190adf670a5a11c8182 |
completed | March 20, 2026, 4:02 p.m. |
Created at: March 12, 2026, 11:12 p.m.