Triple

T34962486
Position Surface form Disambiguated ID Type / Status
Subject Missouri–Oklahoma border E1008295 entity
Predicate hasAdjacentRegionOnMissouriSide P195558 FINISHED
Object southwestern Missouri 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: southwestern Missouri | Statement: [Missouri–Oklahoma border, hasAdjacentRegionOnMissouriSide, southwestern Missouri]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdjacentRegionOnMissouriSide
Context triple: [Missouri–Oklahoma border, hasAdjacentRegionOnMissouriSide, southwestern Missouri]
  • A. hasNeighboringStateToWest
    Indicates that one state is geographically located directly to the west of another state, sharing a common border.
  • B. locatedNearStateBorderWith
    Indicates that one entity is situated geographically close to the border of a specified state.
  • C. borderingOpposingState
    Indicates that one state shares a border with another state that is politically, militarily, or ideologically opposed to it.
  • D. hasNearbyCountyBorder
    Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
  • E. hasNearbyCityOnIndianaSide
    Indicates that an entity has a nearby city located on the Indiana side of a border or region.
  • F. None of above. chosen

Provenance (4 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_69f76dc69564819099e9e78aed6ff0a6 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fdd92396788190ae1424bc1ae55844 completed May 8, 2026, 12:37 p.m.
PD Predicate disambiguation batch_69fdd678f40481909a717a2daec83b36 completed May 8, 2026, 12:26 p.m.
PDg Predicate description generation batch_69fdd922d73c81908ad3faade247ec16 completed May 8, 2026, 12:37 p.m.
Created at: May 3, 2026, 4 p.m.