Triple
T2842302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann van Beethoven |
E62496
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Johann |
E27352
|
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: Johann | Statement: [Johann van Beethoven, givenName, Johann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Johann Context triple: [Johann van Beethoven, givenName, Johann]
-
A.
Johann
chosen
Johann is a given name of Germanic origin commonly used in German-speaking and other European countries.
-
B.
Johannes
Johannes is the given first name of Paul Kruger, the prominent 19th-century Boer leader and president of the South African Republic.
-
C.
Christoph
Christoph is the given name of Christoph Willibald Gluck, the influential 18th-century composer known for reforming opera.
-
D.
Moritz
Moritz is a masculine given name of German origin, commonly used in German-speaking countries.
-
E.
Johan
Johan is the given first name of J. Erik Jonsson, an American businessman and philanthropist who co-founded Texas Instruments and served as mayor of Dallas.
- 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_69ab4c3d16bc81908b3a1c98fbd287fe |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf1898748190b031a2bd2091c0c0 |
completed | March 7, 2026, 8:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1de87779c8190ae6833b80d34f5b2 |
completed | March 11, 2026, 9:28 p.m. |
Created at: March 6, 2026, 10:01 p.m.