Triple

T11122567
Position Surface form Disambiguated ID Type / Status
Subject Ruzhany E263052 entity
Predicate nearbyCity P350 FINISHED
Object Pruzhany E493390 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: Pruzhany | Statement: [Ruzhany, nearbyCity, Pruzhany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pruzhany
Context triple: [Ruzhany, nearbyCity, Pruzhany]
  • A. Pruzhany chosen
    Pruzhany is a historic town in western Belarus known for its cultural heritage and role as a local administrative and economic center.
  • B. Pińsk
    Pińsk is a historic city in present-day Belarus, known as a cultural and religious center of the Polesia region and formerly part of the eastern borderlands of Poland (Kresy).
  • C. Nesvizh
    Nesvizh is a historic town in Belarus renowned for the UNESCO-listed Nesvizh Castle, a former Radziwiłł family residence and one of the country’s most important architectural and cultural landmarks.
  • D. Sieradz
    Sieradz is one of the oldest towns in central Poland, historically significant as a regional center and former royal city.
  • E. Włodawa
    Włodawa is a town in eastern Poland near the borders with Belarus and Ukraine, known for its multicultural heritage and proximity to the former Sobibor extermination camp.
  • 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_69d6aa9b46cc8190b19f9f0cc45bf322 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d79afa0ab88190ab6d61df8cf485ec completed April 9, 2026, 12:26 p.m.
NED1 Entity disambiguation (via context triple) batch_69e462f5fe708190835e427b6bf99f13 completed April 19, 2026, 5:07 a.m.
Created at: April 8, 2026, 9:28 p.m.