Triple
T6717440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mateo |
E153306
|
entity |
| Predicate | isVariantOf |
P455
|
FINISHED |
| Object | Matija |
E354155
|
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: Matija | Statement: [Mateo, isVariantOf, Matija]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Matija Context triple: [Mateo, isVariantOf, Matija]
-
A.
Matija
chosen
Matija is a South Slavic given name, equivalent to the English name Matthew.
-
B.
Luka
Luka is a central character in Maxim Gorky's play "The Lower Depths," known as a compassionate wanderer whose comforting lies and philosophical outlook profoundly affect the other destitute inhabitants of the shelter.
-
C.
Ilija
Ilija is a masculine given name of Slavic origin, commonly used in countries such as Bulgaria, Serbia, and North Macedonia.
-
D.
Vlatko
Vlatko is a masculine given name commonly used in Slavic countries, particularly in North Macedonia and other parts of the Balkans.
-
E.
Saša
Saša is a given name commonly used in Slavic countries, often as a diminutive of Aleksandar or Aleksandra.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d12765a48190b485176dc2ffa0fa |
completed | March 27, 2026, 6:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70afa805c819098312fc0d06ec115 |
completed | March 27, 2026, 10:55 p.m. |
Created at: March 27, 2026, 2:07 p.m.