Triple

T15423540
Position Surface form Disambiguated ID Type / Status
Subject Berdychiv E369445 entity
Predicate connectedByRailTo P848 FINISHED
Object Zhytomyr E62033 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: Zhytomyr | Statement: [Berdychiv, connectedByRailTo, Zhytomyr]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Zhytomyr
Context triple: [Berdychiv, connectedByRailTo, Zhytomyr]
  • A. Zhytomyr chosen
    Zhytomyr is a historic city in northwestern Ukraine known as an important regional center and the birthplace of pioneering rocket engineer Sergei Korolev.
  • B. Khmelnytskyi
    Khmelnytskyi is a regional city in western Ukraine known as an important administrative, economic, and cultural center.
  • C. Vinnytsia
    Vinnytsia is a major city in central Ukraine known as an important administrative, economic, and cultural center on the Southern Bug River.
  • D. Nizhyn
    Nizhyn is a historic city in northern Ukraine known for its cultural heritage, educational institutions, and well-preserved architecture.
  • E. Chernihiv
    Chernihiv is a historic city in northern Ukraine known for its ancient churches, rich cultural heritage, and role as a regional administrative and memorial center.
  • 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_69d85a1849f48190bf898068b2806fae completed April 10, 2026, 2:02 a.m.
NER Named-entity recognition batch_69e03ec032548190840b558dde6057c7 completed April 16, 2026, 1:43 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffb0319f248190a37c9afa09c32428 completed May 9, 2026, 10:07 p.m.
Created at: April 10, 2026, 3:20 a.m.