Triple
T15705649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reinhard Scheer |
E380701
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Reinhard |
E74166
|
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: Reinhard | Statement: [Reinhard Scheer, givenName, Reinhard]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Reinhard Context triple: [Reinhard Scheer, givenName, Reinhard]
-
A.
Reinhard
chosen
Reinhard is a masculine German given name historically borne by several notable figures, including high-ranking officials in Nazi Germany.
-
B.
Eckhard
Eckhard is a masculine given name of German origin, commonly used in German-speaking countries.
-
C.
Helmuth
Helmuth is a masculine given name of German origin, historically borne by several notable military and political figures.
-
D.
Heinrici
Heinrici is a German surname most notably associated with Gotthard Heinrici, a senior Wehrmacht general during World War II.
-
E.
Reimund
Reimund is a masculine given name, primarily used in German-speaking regions, that is a variant of the name Raymond.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04f6fc3608190a85b25755f5345db |
completed | April 16, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff997fe6f48190813bde2bfc11c253 |
completed | May 9, 2026, 8:30 p.m. |
Created at: April 10, 2026, 4:45 a.m.