Triple

T850894
Position Surface form Disambiguated ID Type / Status
Subject Slovenia E18381 entity
Predicate hasHistoricCity P3786 FINISHED
Object Ljubljana E32117 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: Ljubljana | Statement: [Slovenia, hasHistoricCity, Ljubljana]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ljubljana
Context triple: [Slovenia, hasHistoricCity, Ljubljana]
  • A. Ljubljana chosen
    Ljubljana is the capital and largest city of Slovenia, known for its picturesque old town, Baroque and Art Nouveau architecture, and vibrant cultural scene along the Ljubljanica River.
  • B. Zagreb
    Zagreb is the capital and largest city of Croatia, known as a political, cultural, and economic hub in the Balkans.
  • C. Novo Mesto, Slovenia
    Novo Mesto is a historic town in southeastern Slovenia known for its cultural heritage and picturesque setting on the Krka River.
  • D. Siscia
    Siscia was an important ancient Roman city and military center in the province of Pannonia, located at the site of modern-day Sisak in Croatia.
  • E. Nova Gorica
    Nova Gorica is a Slovenian town on the border with Italy, known for its post-World War II development as a planned city and its close integration with the neighboring Italian town of Gorizia.
  • 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_69a4938b04208190b82e1df6b572c548 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac215194819099e6bc1b5df58fb3 completed March 1, 2026, 9:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac11907a988190945e5e5ec8a26ccf completed March 7, 2026, 11:52 a.m.
Created at: March 1, 2026, 7:38 p.m.