Triple

T455819
Position Surface form Disambiguated ID Type / Status
Subject Oklahoma E7229 entity
Predicate containsCity P294 FINISHED
Object Tulsa E39620 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: [Oklahoma, containsCity, Tulsa]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tulsa
Context triple: [Oklahoma, containsCity, Tulsa]
  • A. Tulsa, Oklahoma, United States chosen
    Tulsa is a major city in northeastern Oklahoma known for its historic oil industry, distinctive Art Deco architecture, and role as a cultural and economic hub of the region.
  • B. Enid
    Enid is a feminine given name of Welsh origin, traditionally associated with meanings like "soul" or "life."
  • C. Omaha, Nebraska
    Omaha, Nebraska is the largest city in the state of Nebraska, known as a major Midwestern economic and cultural hub situated along the Missouri River.
  • D. Little Rock, Arkansas
    Little Rock, Arkansas is the capital and largest city of the U.S. state of Arkansas, known as a regional center for government, commerce, and culture.
  • E. Dodge City, Kansas
    Dodge City, Kansas is a historic frontier town in southwestern Kansas known for its Old West heritage, cattle trade history, and role as a major stop along the Santa Fe Trail.
  • 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_69a2e7e5c5bc8190a1dc8178218fba40 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ef9f772c8190863399c5ee1378fe completed Feb. 28, 2026, 1:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69a4746c304881909deb0fdcde69c1c5 completed March 1, 2026, 5:16 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.