Triple

T2579682
Position Surface form Disambiguated ID Type / Status
Subject Broken Arrow E57058 entity
Predicate locatedNear P294 FINISHED
Object Tulsa E185942 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: Tulsa | Statement: [Broken Arrow, locatedNear, Tulsa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tulsa
Context triple: [Broken Arrow, locatedNear, Tulsa]
  • A. Tulsa chosen
    Tulsa is a major city in northeastern Oklahoma known for its historic oil industry, distinctive Art Deco architecture, and vibrant arts and cultural scene.
  • B. Tulsa metropolitan area
    The Tulsa metropolitan area is a regional urban and economic hub in northeastern Oklahoma centered on the city of Tulsa and its surrounding communities.
  • C. Lawton
    Lawton is a mid-sized city in southwestern Oklahoma known as a regional economic and cultural center near Fort Sill and the Wichita Mountains.
  • D. McAlester
    McAlester is a regional hub city in southeastern Oklahoma known for its role as a commercial center and for housing the Oklahoma State Penitentiary.
  • E. Ardmore, Oklahoma
    Ardmore, Oklahoma is a small city in southern Oklahoma known as a regional commercial and transportation hub between Oklahoma City and Dallas, near Lake Texoma.
  • 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_69ab4a4dca6481908c301f8e317396e7 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd3a9fd3c8190a521931e40cd801c completed March 7, 2026, 7:28 a.m.
NED1 Entity disambiguation (via context triple) batch_69afe88781ec8190a13784501208c5a5 completed March 10, 2026, 9:46 a.m.
Created at: March 6, 2026, 9:49 p.m.