Triple

T12116473
Position Surface form Disambiguated ID Type / Status
Subject Stow, Ohio, United States E288574 entity
Predicate borderedBy P224 FINISHED
Object Kent, Ohio E156899 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: Kent, Ohio | Statement: [Stow, Ohio, United States, borderedBy, Kent, Ohio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kent, Ohio
Context triple: [Stow, Ohio, United States, borderedBy, Kent, Ohio]
  • A. Kent, Ohio chosen
    Kent, Ohio is a city in northeastern Ohio best known as the home of Kent State University.
  • B. Lexington, Ohio
    Lexington, Ohio is a small village in north-central Ohio known for its community-oriented atmosphere and proximity to the Mid-Ohio Sports Car Course.
  • C. Kettering, Ohio
    Kettering, Ohio is a suburban city near Dayton known for its residential communities, parks, and role as a commercial and cultural hub in the Miami Valley region.
  • D. Dayton, Kentucky
    Dayton, Kentucky is a small Ohio River city in northern Kentucky, located across from Cincinnati and known as part of the greater Cincinnati metropolitan area.
  • E. Covington, Ohio
    Covington, Ohio is a small village in western Ohio known for its rural character and tight-knit community within the Dayton metropolitan area.
  • 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_69d6ab4a5c448190a110d1273314b21a completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d9156921dc8190aa132b0ab3a7c184 completed April 10, 2026, 3:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69f60a75f77881908345a585a689f69f completed May 2, 2026, 2:30 p.m.
Created at: April 8, 2026, 9:49 p.m.