Triple
T20748216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joachim Frederick, Elector of Brandenburg |
E510644
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Joachim |
—
|
NE NERFINISHED |
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: Joachim | Statement: [Joachim Frederick, Elector of Brandenburg, givenName, Joachim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Joachim Context triple: [Joachim Frederick, Elector of Brandenburg, givenName, Joachim]
-
A.
Joachim
chosen
Joachim is a masculine given name of Hebrew origin, commonly used in German-speaking and other European countries.
-
B.
Joachim
Joachim is a track featured in the rhythm-based game Parabola.
-
C.
Johann
Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
-
D.
Joachim von Kortzfleisch
Joachim von Kortzfleisch was a German Wehrmacht general during World War II, known for his role in the suppression of the 20 July 1944 plot against Adolf Hitler.
-
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 (2 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_69e0b4c845e88190b4c5f3ae79291182 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c226fbf881909794eff3ee9e206b |
completed | April 21, 2026, 12:17 a.m. |
Created at: April 16, 2026, 12:33 p.m.