Triple
T638488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Busch |
E16678
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Ernst |
E81465
|
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: Ernst | Statement: [Ernst Busch, givenName, Ernst]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ernst Context triple: [Ernst Busch, givenName, Ernst]
-
A.
Ernst
chosen
Ernst is a masculine given name of Germanic origin, commonly used in German-speaking and Scandinavian countries.
-
B.
Erwin
Erwin is a masculine given name of German origin, historically associated with figures such as the World War II field marshal Erwin Rommel.
-
C.
Hermann
Hermann Minkowski was a German mathematician best known for developing the geometric formulation of special relativity using four-dimensional spacetime.
-
D.
Helmut
Helmut is a masculine given name of German origin, historically common in German-speaking countries.
-
E.
Bernhard
Bernhard is a male given name of Germanic origin, historically borne by various European nobles and royals, including Prince Bernhard of the Netherlands.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ee95b188190a67b12e1899bcdda |
completed | March 1, 2026, 8:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a64a4ba2d88190969e7c777a1bbfd7 |
completed | March 3, 2026, 2:41 a.m. |
Created at: March 1, 2026, 7:35 p.m.