Triple

T8011565
Position Surface form Disambiguated ID Type / Status
Subject Moscow Governorate E186504 entity
Predicate hasMajorCity P316 FINISHED
Object Voskresensk E138871 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: Voskresensk | Statement: [Moscow Governorate, hasMajorCity, Voskresensk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Voskresensk
Context triple: [Moscow Governorate, hasMajorCity, Voskresensk]
  • A. Voskresensk chosen
    Voskresensk is a town in Moscow Oblast, Russia, known for its industrial base and strong ice hockey tradition.
  • B. Bogoroditsk
    Bogoroditsk is a small historic town in western Russia known for its 18th-century palace-and-park ensemble and its role as a local industrial and cultural center.
  • C. Bogorodsk
    Bogorodsk is a historic Russian town that developed as a regional center of trade and crafts within the former Moscow Governorate.
  • D. Yakutsk Ostrog
    Yakutsk Ostrog was a 17th-century Russian fortified settlement in Siberia that served as the original military and administrative outpost from which the modern city of Yakutsk developed.
  • E. Krasnopresnenskaya
    Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
  • 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_69ca82abaffc8190ab8af79cdbc31ab3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3d722fbc8190b22745b581421f16 completed March 31, 2026, 3:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc63c1f76881909ad6d7777090f2e2 completed April 1, 2026, 12:16 a.m.
Created at: March 30, 2026, 5:19 p.m.