Triple

T12640675
Position Surface form Disambiguated ID Type / Status
Subject Grodno Region E301887 entity
Predicate hasBorderCrossing P4105 FINISHED
Object Privalka E503538 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: Privalka | Statement: [Grodno Region, hasBorderCrossing, Privalka]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Privalka
Context triple: [Grodno Region, hasBorderCrossing, Privalka]
  • A. Pravonín
    Pravonín is a small municipality and village in the Central Bohemian Region of the Czech Republic.
  • B. Pervalka chosen
    Pervalka is a small, tranquil fishing village and resort settlement on Lithuania’s Curonian Spit, known for its scenic dunes, wooden houses, and quiet coastal atmosphere.
  • C. Piravom
    Piravom is a small town in the Indian state of Kerala known for its temples, churches, and scenic location along the Muvattupuzha River.
  • D. Pavka
    Pavka is a diminutive or affectionate nickname commonly used for the Slavic given name Pavel.
  • E. Mojstrovka
    Mojstrovka is a prominent mountain peak in the Julian Alps of Slovenia, popular with hikers and climbers for its scenic alpine views.
  • 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_69d7bdec9f9c8190b4bac675b7588211 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d9614ae6ac8190b42acbf2b0331fda completed April 10, 2026, 8:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69f668754acc8190b5585dbd35387867 completed May 2, 2026, 9:11 p.m.
Created at: April 9, 2026, 5:17 p.m.