Triple

T7959557
Position Surface form Disambiguated ID Type / Status
Subject Orange River region E184825 entity
Predicate usedAsBoundary P71578 FINISHED
Object colonial boundaries in southern Africa LITERAL 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: colonial boundaries in southern Africa | Statement: [Orange River region, usedAsBoundary, colonial boundaries in southern Africa]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedAsBoundary
Context triple: [Orange River region, usedAsBoundary, colonial boundaries in southern Africa]
  • A. isBoundaryFor chosen
    Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
  • B. boundaryBetween
    Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
  • C. hasBoundaryUnit
    Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
  • D. setsBoundary
    Indicates that one entity defines or forms the limiting edge or border of another entity.
  • E. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • 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_69ca8293a2388190aace944d7ed9c0c0 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb3b80050c81909b2db95ade495052 completed March 31, 2026, 3:12 a.m.
PD Predicate disambiguation batch_69cb0473d7dc8190a25d0cf460b9fcbe completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:11 p.m.