Triple

T34962487
Position Surface form Disambiguated ID Type / Status
Subject Missouri–Oklahoma border E1008295 entity
Predicate hasAdjacentRegionOnOklahomaSide P195605 FINISHED
Object northeastern Oklahoma 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: northeastern Oklahoma | Statement: [Missouri–Oklahoma border, hasAdjacentRegionOnOklahomaSide, northeastern Oklahoma]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasAdjacentRegionOnOklahomaSide
Context triple: [Missouri–Oklahoma border, hasAdjacentRegionOnOklahomaSide, northeastern Oklahoma]
  • A. hasAdjacentRegionOnMissouriSide
    Indicates that one region is directly next to another region, with the adjacency occurring on the Missouri side of their shared boundary.
  • B. relativeToOtherOklahomaRegions
    Indicates a spatial or contextual relationship defined in terms of other regions within Oklahoma.
  • C. hasNeighboringStateToWest
    Indicates that one state is geographically located directly to the west of another state, sharing a common border.
  • D. hasNeighbouringState
    Indicates that one state shares a common border or is directly adjacent geographically to another state.
  • E. hasNearbyCountyBorder
    Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
  • 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_69fddac4e2f48190a9301d3422658b29 completed May 8, 2026, 12:44 p.m.
PD Predicate disambiguation batch_69fdda06969c8190b5d033964ea2a690 completed May 8, 2026, 12:41 p.m.
PDg Predicate description generation batch_69fddac42c4081908568649058e86458 completed May 8, 2026, 12:44 p.m.
Created at: May 3, 2026, 4 p.m.