Triple

T9499526
Position Surface form Disambiguated ID Type / Status
Subject Ramenki E229098 entity
Predicate namedAfter P63 FINISHED
Object Ramenki District E285361 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: Ramenki District | Statement: [Ramenki, namedAfter, Ramenki District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ramenki District
Context triple: [Ramenki, namedAfter, Ramenki District]
  • A. Ramenki District chosen
    Ramenki District is a residential and educational area in western Moscow, known for its universities, green spaces, and proximity to major city transport routes.
  • B. Gusu District
    Gusu District is the central urban district of Suzhou, China, known for its historic canals, classical gardens, and well-preserved ancient cityscape.
  • C. Inukami District
    Inukami District is a rural administrative district in Shiga Prefecture, Japan, known for its small towns and scenic countryside.
  • D. Govuro District
    Govuro District is an administrative district located in Inhambane Province in southern Mozambique.
  • E. Bikinsky District
    Bikinsky District is an administrative and municipal district in Khabarovsk Krai in Russia, known for its rural localities and position in the Russian Far East.
  • 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_69ca84753660819098e8d416e89e26ae completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd983a94c48190a7ddf95a953c4ecc completed April 1, 2026, 10:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69d13a0a5ec881908bb1643d2bea2c9f completed April 4, 2026, 4:19 p.m.
Created at: March 30, 2026, 7:56 p.m.