Triple
T1321477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anton |
E28227
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Antun |
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: Antun | Statement: [Anton, hasVariant, Antun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antun Context triple: [Anton, hasVariant, Antun]
-
A.
Anton
chosen
Anton is a masculine given name of Latin origin, commonly used in various European and Slavic countries.
-
B.
Anif
Anif is a small Austrian municipality near Salzburg, known for its historic castle and as a residence of notable figures.
-
C.
Antonin
Antonin is a masculine given name most notably borne by Antonin Scalia, a former Associate Justice of the United States Supreme Court.
-
D.
Smidovich
Smidovich is an urban-type settlement in Russia’s Jewish Autonomous Oblast, serving as a local administrative and population center in the region.
-
E.
Antonovich
Antonovich is the patronymic of Ivan VI of Russia, indicating he was the son of a man named Anton.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c19932888190a3d45871e84f112e |
completed | March 1, 2026, 10:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69acbaf6a6d08190b8a30c2c64f15f59 |
completed | March 7, 2026, 11:55 p.m. |
Created at: March 1, 2026, 7:55 p.m.