Triple

T9282170
Position Surface form Disambiguated ID Type / Status
Subject Peja E223094 entity
Predicate historicalRegion P915 FINISHED
Object Metohija E311399 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: Metohija | Statement: [Peja, historicalRegion, Metohija]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Metohija
Context triple: [Peja, historicalRegion, Metohija]
  • A. Metohija chosen
    Metohija is a historical region in western Kosovo known for its fertile plains and numerous medieval Serbian Orthodox monasteries.
  • B. Morača
    Morača is a major river in Montenegro that flows through the capital city of Podgorica before emptying into Lake Skadar.
  • C. Terazije
    Terazije is a central and historic square in Belgrade, Serbia, known as a major commercial, cultural, and transport hub of the city.
  • D. Paraćin
    Paraćin is a town in central Serbia known as an industrial and transportation hub in the Pomoravlje region.
  • E. Мачва
    Мачва is a historical and geographical region in northwestern Serbia, situated between the Sava and Drina rivers and known for its fertile plains and agricultural significance.
  • 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_69ca842123588190b3f2e1a69037d141 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd081c2b048190aa6930de3bf2f87f completed April 1, 2026, 11:57 a.m.
NED1 Entity disambiguation (via context triple) batch_69d0b209a5b48190a7e6d983bcda5363 completed April 4, 2026, 6:39 a.m.
Created at: March 30, 2026, 7:34 p.m.