Triple

T20737111
Position Surface form Disambiguated ID Type / Status
Subject Obluchensky District E509739 entity
Predicate hasUrbanTypeSettlement P40854 FINISHED
Object Obluchye NE NERFINISHED

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: Obluchye | Statement: [Obluchensky District, hasUrbanTypeSettlement, Obluchye]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Obluchye
Context triple: [Obluchensky District, hasUrbanTypeSettlement, Obluchye]
  • A. Obluchye chosen
    Obluchye is a small town in Russia’s Far East, located in the Jewish Autonomous Oblast and known primarily as a local railway and administrative center.
  • B. Volochysk
    Volochysk is a town in western Ukraine known as a local administrative and transportation center near the border with Ternopil Oblast.
  • C. Terebovlia
    Terebovlia is a historic town in western Ukraine known for its medieval fortress ruins and role as a regional cultural center.
  • D. Bolkhov
    Bolkhov is a historic town in western Russia known for its old churches and traditional architecture within Oryol Oblast.
  • E. Dubrovitsy
    Dubrovitsy is a historic rural locality in Moscow Oblast, Russia, known for its ornate baroque Church of the Theotokos of the Sign and its scenic setting near the city of Podolsk.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4c589c08190834fb5d86d0efa2b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c20ac6e881908524be890be699e7 completed April 21, 2026, 12:17 a.m.
Created at: April 16, 2026, 12:32 p.m.