Triple
T8643036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksandar Mitrović |
E204701
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Aleksandar |
E307305
|
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: Aleksandar | Statement: [Aleksandar Mitrović, givenName, Aleksandar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Aleksandar Context triple: [Aleksandar Mitrović, givenName, Aleksandar]
-
A.
Aleksandar
chosen
Aleksandar is a masculine given name commonly used in Slavic countries, equivalent to Alexander.
-
B.
Jovan
Jovan is a masculine given name commonly used in South Slavic regions, equivalent to "John" in English.
-
C.
Ivan Sratsimir
Ivan Sratsimir was a 14th-century Bulgarian tsar who ruled the Vidin-based western part of the fragmented Second Bulgarian Empire during its final decades before Ottoman conquest.
-
D.
Dimitar
Dimitar is a masculine given name of Slavic origin, commonly used in Bulgaria and other Eastern European countries.
-
E.
Milutin
Milutin is a masculine given name of Slavic origin, commonly used in Serbian and other South Slavic cultures.
- 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_69ca834ca1c88190a11ffb0200342fac |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc479720f481908ee2b12c2775e76a |
completed | March 31, 2026, 10:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf28516bd08190b69b314aea423d22 |
completed | April 3, 2026, 2:39 a.m. |
Created at: March 30, 2026, 6:28 p.m.