Triple

T26325424
Position Surface form Disambiguated ID Type / Status
Subject Trans-Olza region E662238 entity
Predicate borderDisputeInvolved P49394 FINISHED
Object Poland–Czechoslovakia border dispute 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: Poland–Czechoslovakia border dispute | Statement: [Trans-Olza region, borderDisputeInvolved, Poland–Czechoslovakia border dispute]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: borderDisputeInvolved
Context triple: [Trans-Olza region, borderDisputeInvolved, Poland–Czechoslovakia border dispute]
  • A. borderDisputeResolvedBy
    Indicates that a previously contested border between entities has been settled or resolved through the specified agent, process, or agreement.
  • B. borderDisputesWith chosen
    Indicates that there are contested or unresolved boundary claims between two entities.
  • C. borderDisputeRelatedLanguage
    Indicates a relationship where the language is associated with, used in, or relevant to a border dispute between entities.
  • D. borderDisputeConstitutionalProvisionInvoked
    Indicates that a constitutional provision is cited or relied upon in the context of a border dispute between entities.
  • E. borderDisputeNegotiationChannel
    Indicates a communication or diplomatic channel used specifically for negotiating the resolution of a border dispute between parties.
  • F. None of above.

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_69ee812f32748190871d970c4e2a8ddf completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f7675b12848190a3569cfda29c5b0e completed May 3, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69f762f4b59481909f70074f11825bfb completed May 3, 2026, 3 p.m.
Created at: April 26, 2026, 10:30 p.m.