Triple
T1676176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antoni |
E36235
|
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: [Antoni, hasVariant, Antun]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Antun Context triple: [Antoni, hasVariant, Antun]
-
A.
Anto
Anto is a diminutive given name, commonly used as a short form of names like Anton or Antonio in various European and Slavic cultures.
-
B.
Anton
chosen
Anton is a masculine given name of Latin origin, commonly used in various European and Slavic countries.
-
C.
Anif
Anif is a small Austrian municipality near Salzburg, known for its historic castle and as a residence of notable figures.
-
D.
Atoni
Atoni are an indigenous ethnic group of western Timor known for their traditional hierarchical social structure, distinctive architecture, and dryland farming culture.
-
E.
Antoshka
Antoshka is a common Russian diminutive form of the male given name Anton, often used affectionately or informally.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa625cb1a08190bf7b138c5bfb90b2 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad798b0f1c81908174b312878e559b |
completed | March 8, 2026, 1:28 p.m. |
Created at: March 4, 2026, 7:29 p.m.