Triple

T1051662
Position Surface form Disambiguated ID Type / Status
Subject Subcarpathian Voivodeship E22711 entity
Predicate hasRegionalCapital P3877 FINISHED
Object Rzeszów E220683 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: Rzeszów | Statement: [Subcarpathian Voivodeship, hasRegionalCapital, Rzeszów]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rzeszów
Context triple: [Subcarpathian Voivodeship, hasRegionalCapital, Rzeszów]
  • A. Rzeszów chosen
    Rzeszów is a major city in southeastern Poland known as an important economic, academic, and cultural center of the region.
  • B. Przemyśl
    Przemyśl is a historic city in southeastern Poland near the Ukrainian border, known for its strategic location, multicultural heritage, and well-preserved fortifications.
  • C. Tarnów
    Tarnów is a historic city in southern Poland known for its well-preserved Old Town, Renaissance architecture, and cultural heritage.
  • D. Bielsko-Biała
    Bielsko-Biała is a city in southern Poland at the foot of the Beskid Mountains, known as a regional industrial and cultural center formed from the historic towns of Bielsko and Biała.
  • E. Kielce
    Kielce is a city in south-central Poland known as an important regional center for industry, education, and culture.
  • 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_69a493da02e081908c13ff5e02a0fe7a completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4b8b5312081909796df58fa7c1e9d completed March 1, 2026, 10:07 p.m.
NED1 Entity disambiguation (via context triple) batch_69ae26ce527c8190988fd9a97ad06895 completed March 9, 2026, 1:47 a.m.
Created at: March 1, 2026, 7:42 p.m.