Triple

T20587488
Position Surface form Disambiguated ID Type / Status
Subject Six Flags St. Louis E505823 entity
Predicate location P40 FINISHED
Object Eureka, Missouri NE NERFINISHED

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: Eureka, Missouri | Statement: [Six Flags St. Louis, location, Eureka, Missouri]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eureka, Missouri
Context triple: [Six Flags St. Louis, location, Eureka, Missouri]
  • A. Eureka, Missouri chosen
    Eureka, Missouri is a suburban city in the Greater St. Louis area known for being home to the Six Flags St. Louis amusement park.
  • B. Eugene, Missouri
    Eugene, Missouri is a small unincorporated community in central Missouri located within Cole County.
  • C. Urich, Missouri
    Urich, Missouri is a small rural village located in Henry County in the western part of the state.
  • D. Ewing, Missouri
    Ewing, Missouri is a small rural community located in Lewis County in the northeastern part of the state.
  • E. Van Buren, Missouri
    Van Buren, Missouri is a small town in the Ozarks that serves as a popular gateway for outdoor recreation along the Current and Jacks Fork rivers.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b4b9669c8190b8e81fc72817d42c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a977fb18819085fee5cf5d45c1b0 completed April 20, 2026, 10:32 p.m.
Created at: April 16, 2026, 11:40 a.m.