Triple

T22120498
Position Surface form Disambiguated ID Type / Status
Subject Ersekë E546652 entity
Predicate nearbyCity P350 FINISHED
Object Korçë NE NERFINISHED

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: Korçë | Statement: [Ersekë, nearbyCity, Korçë]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Korçë
Context triple: [Ersekë, nearbyCity, Korçë]
  • A. Korçë chosen
    Korçë is a city in southeastern Albania known as a cultural and educational center with rich Orthodox Christian heritage and historic architecture.
  • B. Gjirokastër
    Gjirokastër is a historic stone-built city in southern Albania, recognized as a UNESCO World Heritage Site for its well-preserved Ottoman-era architecture.
  • C. Kukës
    Kukës is a northeastern Albanian city near the border with Kosovo, known for its mountainous surroundings and its role as a refuge during the Kosovo War.
  • D. Krujë
    Krujë is a historic town in central Albania known as the stronghold of national hero Skanderbeg and a symbol of Albanian resistance to the Ottoman Empire.
  • E. Lezhë
    Lezhë is a historic town in northwestern Albania, known as the site of the League of Lezhë and for its cultural and archaeological heritage.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e38b3848190ac3a4fa97d56e65a completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f12951fcd48190841319cd879c15cb completed April 28, 2026, 9:40 p.m.
Created at: April 16, 2026, 8:31 p.m.