Triple
T6141687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Ulrich of Brunswick |
E136976
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Anton |
E28227
|
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: Anton | Statement: [Anthony Ulrich of Brunswick, givenName, Anton]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anton Context triple: [Anthony Ulrich of Brunswick, givenName, Anton]
-
A.
Anton
chosen
Anton is a masculine given name of Latin origin, commonly used in various European and Slavic countries.
-
B.
Andrei
Andrei is a masculine given name commonly used in Slavic and Eastern European countries, equivalent to the English name Andrew.
-
C.
Anatole
Anatole is the famously temperamental and gifted French chef employed by Aunt Dahlia in P. G. Wodehouse’s Jeeves and Wooster stories.
-
D.
Rodion
Rodion is a masculine given name of Slavic origin, most notably borne by Soviet military commander Rodion Malinovsky.
-
E.
Emil
Emil is a masculine given name used in various European languages, often associated with Latin and Germanic origins.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb2404c8190bbbfa78d5f49389f |
completed | March 22, 2026, 9:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c135f2defc8190a666f82e230a51c2 |
completed | March 23, 2026, 12:45 p.m. |
Created at: March 22, 2026, 4:16 p.m.