Triple

T12756753
Position Surface form Disambiguated ID Type / Status
Subject Lake Tenkiller E304879 entity
Predicate nearCity P350 FINISHED
Object Vian, Oklahoma E308470 NE 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: Vian, Oklahoma | Statement: [Lake Tenkiller, nearCity, Vian, Oklahoma]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vian, Oklahoma
Context triple: [Lake Tenkiller, nearCity, Vian, Oklahoma]
  • A. Vian, Oklahoma chosen
    Vian, Oklahoma is a small town in Sequoyah County that forms part of the Oklahoma portion of the Fort Smith metropolitan area.
  • B. Wister, Oklahoma
    Wister, Oklahoma is a small town in southeastern Oklahoma known for its proximity to Wister Lake State Park and its location within Le Flore County.
  • C. Hinton, Oklahoma
    Hinton, Oklahoma is a small town in Caddo County known for its proximity to Red Rock Canyon Adventure Park and its location along major regional highways.
  • D. Blanchard, Oklahoma
    Blanchard, Oklahoma is a small city in central Oklahoma that serves as a bedroom community within the Oklahoma City metropolitan area.
  • E. Knowles, Oklahoma
    Knowles, Oklahoma is a small rural town located in the Oklahoma Panhandle region of the United States.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d8b57b88190b29b8fdca415c81c completed April 10, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69fe64e2991c81908f474fe07a6ba10a completed May 8, 2026, 10:34 p.m.
Created at: April 9, 2026, 5:27 p.m.