Triple

T2793495
Position Surface form Disambiguated ID Type / Status
Subject Red River (southeastern boundary area) E61981 entity
Predicate instanceOf P0 FINISHED
Object internationally recognized boundary segment C1689 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: internationally recognized boundary segment
Context triple: [Red River (southeastern boundary area), instanceOf, internationally recognized boundary segment]
  • A. internationally recognized internal boundary
    An internationally recognized internal boundary is an officially acknowledged dividing line within a sovereign state that separates its subnational units (such as states, provinces, or regions) and is accepted by the international community as part of that state's internal territorial organization.
  • B. geographical boundary
    A geographical boundary is a defined line or zone on the Earth's surface that separates distinct political, cultural, or natural regions.
  • C. land border
    A land border is a defined line on the Earth's surface that separates the territories of two adjacent states or regions across contiguous land.
  • D. political boundary
    A political boundary is an officially recognized dividing line that separates the geographic areas of different political entities, such as countries, states, or municipalities, defining the limits of their jurisdiction and authority.
  • E. international border chosen
    An international border is a legally defined geographic boundary that separates the territories and jurisdictions of two or more sovereign states.
  • F. None of above.

Provenance (1 batch)

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_69ab4b7f51d881908768300ebd2fbdae completed March 6, 2026, 9:47 p.m.
Created at: March 6, 2026, 9:58 p.m.