Triple

T14179331
Position Surface form Disambiguated ID Type / Status
Subject Ruse Opera E351411 entity
Predicate location P40 FINISHED
Object Ruse, Bulgaria E70722 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: Ruse, Bulgaria | Statement: [Ruse Opera, location, Ruse, Bulgaria]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruse, Bulgaria
Context triple: [Ruse Opera, location, Ruse, Bulgaria]
  • A. Ruse
    Ruse is a residential suburb in the Macarthur region of Sydney, New South Wales, Australia.
  • B. Ruse chosen
    Ruse is a major Bulgarian city and river port on the Danube, known for its elegant architecture and role as an important economic and transport hub.
  • C. Pazardzhik, Bulgaria
    Pazardzhik is a city in southern Bulgaria known as a regional administrative and cultural center on the banks of the Maritsa River.
  • D. Reutov
    Reutov is a town in western Russia that functions as a suburban satellite of Moscow, known for its residential areas and proximity to the capital.
  • E. Varna
    Varna is a major Bulgarian city on the Black Sea coast known as an important economic, cultural, and maritime center.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61c90abc8190a9b9dc1f50db59fa completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef5c11708190a7fd4c0682b6ed81 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 1:02 a.m.