Triple

T6708679
Position Surface form Disambiguated ID Type / Status
Subject Pinsk E153073 entity
Predicate locatedIn P40 FINISHED
Object Brest Region E209608 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: Brest Region | Statement: [Pinsk, locatedIn, Brest Region]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Brest Region
Context triple: [Pinsk, locatedIn, Brest Region]
  • A. Brest Region chosen
    Brest Region is an administrative region in southwestern Belarus known for its border location with Poland and Ukraine, agricultural importance, and historical sites including the Brest Fortress.
  • B. Brest District
    Brest District is an administrative district in southwestern Belarus that surrounds and is governed from the city of Brest.
  • C. Grodno Region
    Grodno Region is an administrative region in western Belarus known for its historic cities, diverse cultural heritage, and location along the borders with Poland and Lithuania.
  • D. Minsk Region
    Minsk Region is an administrative region in central Belarus that surrounds, but does not include, the national capital city of Minsk.
  • E. Mogilev Region
    Mogilev Region is an administrative region in eastern Belarus known for its industrial centers, agricultural production, and location along the Dnieper River.
  • 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_69c68808d8d8819087369015270788fe completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d1049b7c8190a970a165d15b440b completed March 27, 2026, 6:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7008e6b308190a3d5db2bf4a469c4 completed March 27, 2026, 10:11 p.m.
Created at: March 27, 2026, 2:06 p.m.