Triple

T9826686
Position Surface form Disambiguated ID Type / Status
Subject Perovo E238671 entity
Predicate locatedIn P40 FINISHED
Object Perovo District E238671 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: Perovo District | Statement: [Perovo, locatedIn, Perovo District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Perovo District
Context triple: [Perovo, locatedIn, Perovo District]
  • A. Braničevo District
    Braničevo District is an administrative region in eastern Serbia along the Danube River, known for its historical heritage and important archaeological sites.
  • B. Belgrade District
    Belgrade District is an administrative district in Serbia that encompasses the capital city of Belgrade and its surrounding municipalities.
  • C. Perovo chosen
    Perovo is a Moscow Metro station serving the Kalininsko–Solntsevskaya Line in the Perovo District of eastern Moscow.
  • D. Nišava District
    Nišava District is an administrative district in southeastern Serbia centered around the city of Niš and known as an important regional economic, cultural, and transportation hub.
  • E. Šabac District
    Šabac District is an administrative region in western Serbia centered around the city of Šabac, known for its historical significance and cultural institutions.
  • 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_69ca84e0dd1881909800765d1e21f735 completed March 30, 2026, 2:12 p.m.
NER Named-entity recognition batch_69cdb32370e8819087c85fb8328587be completed April 2, 2026, 12:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d1cc88a86c819088f259a049eec4db completed April 5, 2026, 2:44 a.m.
Created at: March 30, 2026, 8:32 p.m.