Triple

T8691945
Position Surface form Disambiguated ID Type / Status
Subject Chernsky Uyezd E206311 entity
Predicate hasTypeLabel P2396 FINISHED
Object Chernsky Uyezd E206311 NE FINISHED

How this triple was built (3 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: Chernsky Uyezd | Statement: [Chernsky Uyezd, hasTypeLabel, Chernsky Uyezd]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chernsky Uyezd
Context triple: [Chernsky Uyezd, hasTypeLabel, Chernsky Uyezd]
  • A. Chernsky Uyezd chosen
    Chernsky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
  • B. Mtsensky Uyezd
    Mtsensky Uyezd was an administrative district (uyezd) within the Russian Empire, centered around the town of Mtsensk and historically part of the Tula Governorate.
  • C. Livensky Uyezd
    Livensky Uyezd was an administrative district (uyezd) within the former Tula Governorate of the Russian Empire.
  • D. Dankovsky Uyezd
    Dankovsky Uyezd was an administrative subdivision (uyezd) of the former Tula Governorate in the Russian Empire.
  • E. Epifansky Uyezd
    Epifansky Uyezd was an administrative district (uyezd) within the historical Tula Governorate of the Russian Empire.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTypeLabel
Context triple: [Chernsky Uyezd, hasTypeLabel, Chernsky Uyezd]
  • A. hasLabel
    Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
  • B. hasTypeName chosen
    Indicates that an entity is associated with a specific type name used to classify or identify its kind.
  • C. haveType
    Indicates that an entity belongs to or is classified under a specified type or category.
  • D. hasLabelSet
    Indicates that an entity is associated with a specific collection or set of labels.
  • E. hasLevelType
    Indicates that an entity is associated with a specific type or category of level (e.g., difficulty, hierarchy, or stage).
  • F. None of above.

Provenance (4 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_69ca835481fc819084e33d3bc883bfa6 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc5825385081908dee42cba8e98392 completed March 31, 2026, 11:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69cf427fb1988190ab9fd810423ced84 completed April 3, 2026, 4:30 a.m.
PD Predicate disambiguation batch_69cc4569f9048190b9c86b4c81103d35 completed March 31, 2026, 10:06 p.m.
Created at: March 30, 2026, 6:33 p.m.