Triple

T32311539
Position Surface form Disambiguated ID Type / Status
Subject Lower Sioux Indian Community E825511 entity
Predicate landBaseLocatedAlong P2409 FINISHED
Object south bank of the Minnesota River 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: south bank of the Minnesota River | Statement: [Lower Sioux Indian Community, landBaseLocatedAlong, south bank of the Minnesota River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: landBaseLocatedAlong
Context triple: [Lower Sioux Indian Community, landBaseLocatedAlong, south bank of the Minnesota River]
  • A. locatedAlong chosen
    Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
  • B. landBaseFor
    Indicates that one location serves as the primary land-based support or operational base for another entity (such as a unit, activity, or facility).
  • C. landsAt
    Indicates that a moving entity arrives and comes to rest at a specific location or destination.
  • D. likelyLocatedIn
    Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
  • E. oftenLocatedAs
    Indicates that one entity is frequently found or situated in the same place as another entity.
  • 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_69f3491213b88190a57094d8697a7455 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6bdb74c708190833b4c7d332b1a0d completed May 3, 2026, 3:15 a.m.
PD Predicate disambiguation batch_69f6b632cf788190a3d0c08cd026b84b completed May 3, 2026, 2:42 a.m.
Created at: May 1, 2026, 12:46 a.m.