Triple

T12145075
Position Surface form Disambiguated ID Type / Status
Subject Tulskaya E289295 entity
Predicate hasEntranceFrom P1985 FINISHED
Object Tulskaya Square E1006883 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: Tulskaya Square | Statement: [Tulskaya, hasEntranceFrom, Tulskaya Square]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tulskaya Square
Context triple: [Tulskaya, hasEntranceFrom, Tulskaya Square]
  • A. Tulskaya Square chosen
    Tulskaya Square is a public square in Moscow, Russia, known as a transport and urban hub in the city’s southern part.
  • B. Vladimirskaya Square
    Vladimirskaya Square is a central urban square in Saint Petersburg, Russia, known for its historic architecture and proximity to major transport links and cultural landmarks.
  • C. Smolenskaya Square
    Smolenskaya Square is a major public square in central Moscow, known as a key traffic and urban hub near the Arbat district.
  • D. Borovitskaya Square
    Borovitskaya Square is a central Moscow square located by the Kremlin, serving as a key traffic and historical junction near several important cultural and governmental sites.
  • E. Paveletskaya Square
    Paveletskaya Square is a major public square in central Moscow, known as a key transport hub near Paveletsky railway station and surrounding commercial and business areas.
  • 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_69d6ab4c6710819097a9d228382dde43 completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d915aacaa08190b31f54e230334406 completed April 10, 2026, 3:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6a531c62481908eac880e716cf55b completed May 3, 2026, 1:30 a.m.
Created at: April 8, 2026, 9:49 p.m.