Triple

T20511341
Position Surface form Disambiguated ID Type / Status
Subject Moraine Assembly E503569 entity
Predicate locatedIn P40 FINISHED
Object Moraine, Ohio 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: Moraine, Ohio | Statement: [Moraine Assembly, locatedIn, Moraine, Ohio]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Moraine, Ohio
Context triple: [Moraine Assembly, locatedIn, Moraine, Ohio]
  • A. Moraine, Ohio chosen
    Moraine, Ohio is a small industrial city near Dayton known for its history of automobile manufacturing and assembly plants.
  • B. Obetz, Ohio
    Obetz, Ohio is a small village in central Ohio known for its proximity to Columbus and its mix of residential neighborhoods, industrial facilities, and logistics centers.
  • C. Ney, Ohio
    Ney, Ohio is a small village located in Defiance County in the northwestern part of the U.S. state of Ohio.
  • D. Wakeman, Ohio
    Wakeman, Ohio is a small village in northern Ohio known for its rural character and location within Huron County.
  • E. Zoar, Ohio
    Zoar, Ohio is a historic village founded in the early 19th century by German religious separatists, known for its well-preserved communal architecture and role as a notable utopian settlement.
  • 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_69e0b4b2aa788190ae9eb37c1d73b1f1 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e69dcb8f5c8190b0d4c09f3669a8ec completed April 20, 2026, 9:42 p.m.
Created at: April 16, 2026, 11:36 a.m.