Triple

T21808525
Position Surface form Disambiguated ID Type / Status
Subject Lochkov E538410 entity
Predicate hasOfficialName P66 FINISHED
Object Lochkov 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: Lochkov | Statement: [Lochkov, hasOfficialName, Lochkov]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lochkov
Context triple: [Lochkov, hasOfficialName, Lochkov]
  • A. Lochkov chosen
    Lochkov is a district in Prague, Czech Republic, historically known for its geological significance and giving its name to the Lochkovian stage of the Devonian period.
  • B. Gorokhovets
    Gorokhovets is a historic town in Vladimir Oblast, Russia, known for its well-preserved merchant architecture and scenic location amid the forests and hills of central Russia.
  • C. Yukhnov
    Yukhnov is a small historic town in western Russia known for its location on the Ugra River and its role in regional trade and World War II history.
  • D. Zhukovka
    Zhukovka is a rural locality in Moscow Oblast, Russia, situated within the Odintsovsky District and known primarily as a residential settlement near Moscow.
  • E. Polyanka
    Polyanka is a Moscow Metro station on the Serpukhovsko–Timiryazevskaya Line, located near the city center and serving the surrounding Polyanka Street area.
  • 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_69e0c473f0f8819086c9d1b4a143bd67 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f078047ca88190a0efa4bc7f2faf80 completed April 28, 2026, 9:04 a.m.
Created at: April 16, 2026, 6:53 p.m.