Triple

T13415683
Position Surface form Disambiguated ID Type / Status
Subject Eparchy of Žiča E313205 entity
Predicate territoryIncludes P285 FINISHED
Object Kraljevo E314434 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: Kraljevo | Statement: [Eparchy of Žiča, territoryIncludes, Kraljevo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kraljevo
Context triple: [Eparchy of Žiča, territoryIncludes, Kraljevo]
  • A. Kraljevo chosen
    Kraljevo is a city in central Serbia known as a regional administrative and cultural center, situated near several important medieval Serbian monasteries.
  • B. Kruševac
    Kruševac is a historic city in central Serbia founded in the 14th century by Prince Lazar, serving briefly as the capital of his medieval Serbian principality.
  • C. Smederevo
    Smederevo is a historic Serbian city on the Danube River, known for its large medieval fortress and role as a former capital of the Serbian Despotate.
  • D. Kragujevac
    Kragujevac is a central Serbian city historically significant as an early capital and industrial and cultural hub of the country.
  • E. Kumanovo
    Kumanovo is a city in northern North Macedonia known for its historical significance and as the site where the 1999 Kumanovo Agreement ending the Kosovo War was signed.
  • 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_69d806ad0c44819088833ae1ec9e9690 completed April 9, 2026, 8:06 p.m.
NER Named-entity recognition batch_69dbaeb6e904819098cc9153fd2feaf5 completed April 12, 2026, 2:39 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd6471ba348190a0cd1745daff6114 completed May 8, 2026, 4:20 a.m.
Created at: April 9, 2026, 9:39 p.m.