Triple

T8336772
Position Surface form Disambiguated ID Type / Status
Subject Tuapse E195806 entity
Predicate governingBody P46 FINISHED
Object Tuapse town administration E195806 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: Tuapse town administration | Statement: [Tuapse, governingBody, Tuapse town administration]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tuapse town administration
Context triple: [Tuapse, governingBody, Tuapse town administration]
  • A. Tuapse chosen
    Tuapse is a Black Sea port town in southern Russia known as a seaside resort and industrial center within Krasnodar Krai.
  • B. Plesetsk
    Plesetsk is a town in Arkhangelsk Oblast in northwestern Russia known primarily for its proximity to the Plesetsk Cosmodrome, a major Russian space launch facility.
  • C. Sestroretsk
    Sestroretsk is a town in northwestern Russia, now part of Saint Petersburg, historically known for its arms factory and seaside resort area on the Gulf of Finland.
  • D. Nikolskoye
    Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
  • E. Nikolskoye
    Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
  • 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd3fc80819097b326119107ad4d completed March 31, 2026, 8:03 a.m.
NED1 Entity disambiguation (via context triple) batch_69cd95e17300819090e405c4c60b280d completed April 1, 2026, 10:02 p.m.
Created at: March 30, 2026, 5:57 p.m.