Triple

T3850215
Position Surface form Disambiguated ID Type / Status
Subject Zelenogradsky Administrative Okrug E85276 entity
Predicate historicallyDistinctFrom P51926 FINISHED
Object central districts of Moscow LITERAL 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: central districts of Moscow | Statement: [Zelenogradsky Administrative Okrug, historicallyDistinctFrom, central districts of Moscow]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicallyDistinctFrom
Context triple: [Zelenogradsky Administrative Okrug, historicallyDistinctFrom, central districts of Moscow]
  • A. historicallyBorneBy
    Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
  • B. historicallyConsidered
    Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
  • C. historicallyIn
    Indicates that one entity existed, occurred, or was situated within the historical context, period, or jurisdiction associated with another entity.
  • D. historicallyConfusedWith
    Indicates that one entity has been mistaken for or identified as another entity in historical records, interpretations, or traditions.
  • E. historicallyRecognizedAs
    Indicates that an entity has been acknowledged or designated under a particular name, status, or role during a past historical period.
  • F. None of above. chosen

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_69aed936de1c81908f91bed80f70abb2 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeebcf67788190975105131baabc4b completed March 9, 2026, 3:48 p.m.
PD Predicate disambiguation batch_69aee750377c8190af70c79768c0edd8 completed March 9, 2026, 3:29 p.m.
PDg Predicate description generation batch_69aee8d9b328819080158be59e5bcc97 completed March 9, 2026, 3:35 p.m.
Created at: March 9, 2026, 3:19 p.m.