Triple

T22310507
Position Surface form Disambiguated ID Type / Status
Subject Khoroshevskoye Shosse E551498 entity
Predicate hasNameForm P19207 FINISHED
Object Khoroshevskoye Shosse 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: Khoroshevskoye Shosse | Statement: [Khoroshevskoye Shosse, hasNameForm, Khoroshevskoye Shosse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Khoroshevskoye Shosse
Context triple: [Khoroshevskoye Shosse, hasNameForm, Khoroshevskoye Shosse]
  • A. Khoroshevskoye Shosse chosen
    Khoroshevskoye Shosse is a major roadway in Moscow that serves as an important traffic artery connecting central districts with the city’s northwestern areas.
  • B. Pyatnitskoye Shosse
    Pyatnitskoye Shosse is a Moscow Metro station serving as the northwestern terminus of the Arbatsko–Pokrovskaya Line.
  • C. Mozhayskoye Shosse
    Mozhayskoye Shosse is a major highway in western Moscow that continues the city’s main radial route toward the Mozhaysk and Smolensk directions.
  • D. Borovskoye Shosse
    Borovskoye Shosse is a Moscow Metro station on the Kalininsko–Solntsevskaya line serving the Borovskoye Highway area in western Moscow.
  • E. Dmitrovskoye Shosse
    Dmitrovskoye Shosse is a major radial highway in Moscow that connects the city center with its northern suburbs and outlying regions.
  • 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_69e11e46c0188190800181a4233f28fe completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1574e7fc0819080e3e85001ab2c90 completed April 29, 2026, 12:56 a.m.
Created at: April 16, 2026, 8:42 p.m.