Triple

T6238445
Position Surface form Disambiguated ID Type / Status
Subject The Yo E139534 entity
Predicate usedIn P98 FINISHED
Object Youngstown, Ohio E26250 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: Youngstown, Ohio | Statement: [The Yo, usedIn, Youngstown, Ohio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Youngstown, Ohio
Context triple: [The Yo, usedIn, Youngstown, Ohio]
  • A. Youngstown chosen
    Youngstown is an industrial city in northeastern Ohio historically known for its steel production and central role in the Rust Belt’s economic rise and decline.
  • B. Lorain
    Lorain is an industrial city on Lake Erie in northern Ohio, historically known for its steel production and shipbuilding.
  • C. Clyde, Ohio
    Clyde, Ohio is a small city in Sandusky County best known as the childhood home and inspiration for many works of American writer Sherwood Anderson.
  • D. Montgomery, Ohio
    Montgomery, Ohio is a suburban city in Hamilton County near Cincinnati, known for its historic charm, affluent residential character, and well-regarded schools.
  • E. Newark, Ohio
    Newark, Ohio is a mid-sized city in central Ohio known as the county seat of Licking County and a regional hub for industry, education, and transportation.
  • 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_69c008b0e7ac8190808a59573ee646f3 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0630373088190a9d4b1f7e442c129 completed March 22, 2026, 9:45 p.m.
NED1 Entity disambiguation (via context triple) batch_69ca1463cacc8190b143ab1ced648ec7 completed March 30, 2026, 6:12 a.m.
Created at: March 22, 2026, 4:23 p.m.