Triple

T16078957
Position Surface form Disambiguated ID Type / Status
Subject Akhtubinsk E390048 entity
Predicate roadDistanceTo P7750 FINISHED
Object Astrakhan (regional center) E380061 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: Astrakhan (regional center) | Statement: [Akhtubinsk, roadDistanceTo, Astrakhan (regional center)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Astrakhan (regional center)
Context triple: [Akhtubinsk, roadDistanceTo, Astrakhan (regional center)]
  • A. Astrakhan chosen
    Astrakhan is a historic Russian city near the Caspian Sea, known as a key Volga River port and gateway to the Volga Delta region.
  • B. Orenburg
    Orenburg is a major city in southwestern Russia near the Ural River, historically significant as a frontier fortress and administrative center linking European Russia with Central Asia.
  • C. Yelabuga
    Yelabuga is a historic town in the Republic of Tatarstan, Russia, known for its preserved merchant architecture and cultural heritage.
  • D. Cheboksary
    Cheboksary is a major city on the Volga River in western Russia and the capital of the Chuvash Republic.
  • E. Ulyanovka
    Ulyanovka is an urban-type settlement in Leningrad Oblast, Russia, situated within the administrative boundaries of Tosnensky District.
  • 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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e183c401a881908fcb0b753d2dfc8a completed April 17, 2026, 12:50 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe48907148190ab04520717141788 completed May 10, 2026, 1:51 a.m.
Created at: April 10, 2026, 4:57 a.m.