Triple

T15729125
Position Surface form Disambiguated ID Type / Status
Subject South Morava E381293 entity
Predicate majorTributary P415 FINISHED
Object Toplica E1207694 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: Toplica | Statement: [South Morava, majorTributary, Toplica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Toplica
Context triple: [South Morava, majorTributary, Toplica]
  • A. Toplica chosen
    Toplica is a historical region in southern Serbia, known for its medieval significance and association with the early Serbian state under the Nemanjić dynasty.
  • B. Prilep
    Prilep is a historic city in present-day North Macedonia known for its medieval fortresses, Ottoman-era architecture, and role as a regional cultural and economic center.
  • C. Jablanica
    Jablanica is a town in Bosnia and Herzegovina known for its location in the Neretva River valley and its historical World War II railway bridge.
  • D. Jablanica
    Jablanica is a river in western Serbia that serves as one of the headwaters forming the Kolubara River.
  • E. Mladenovac
    Mladenovac is a suburban municipality and town located in the southern part of the City of Belgrade, Serbia.
  • 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_69d86d9cdb648190bf3171be0bd7d872 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e04fb4cc0081909efe330339474017 completed April 16, 2026, 2:55 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f372f7c8190ba04b8bd13bff95c completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 4:46 a.m.