Triple

T4151968
Position Surface form Disambiguated ID Type / Status
Subject Vostochny Cosmodrome E89926 entity
Predicate nearbyCity P350 FINISHED
Object Svobodny E101697 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: Svobodny | Statement: [Vostochny Cosmodrome, nearbyCity, Svobodny]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Svobodny
Context triple: [Vostochny Cosmodrome, nearbyCity, Svobodny]
  • A. Svobodny chosen
    Svobodny is a town in Russia’s Amur Oblast, known historically as a Trans-Siberian Railway hub and more recently for its proximity to the Vostochny Cosmodrome.
  • B. Svoboda
    Svoboda is a common Czech surname borne by numerous notable figures, including politicians, artists, and athletes.
  • C. Privolnoye
    Privolnoye is a rural village in southern Russia best known as the birthplace of former Soviet leader Mikhail Gorbachev.
  • D. Vrijheid
    Vrijheid was a Dutch ship of the line that served as the flagship of the Dutch fleet during the late 18th century and was captured by the British at the Battle of Camperdown in 1797.
  • E. Molodyozhnaya
    Molodyozhnaya is a Moscow Metro station serving the western part of the city on one of its main radial lines.
  • 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_69aed95a59a881909b26e70b42c6811a completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69af0276363081908e4d17684291b547 completed March 9, 2026, 5:25 p.m.
NED1 Entity disambiguation (via context triple) batch_69b57f3707a8819082bafd0d11b7359f completed March 14, 2026, 3:31 p.m.
Created at: March 9, 2026, 3:44 p.m.