Triple

T29436504
Position Surface form Disambiguated ID Type / Status
Subject Osborn, Ohio E746586 entity
Predicate municipalConsolidationWith P80558 FINISHED
Object Fairborn, 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: Fairborn, Ohio | Statement: [Osborn, Ohio, municipalConsolidationWith, Fairborn, Ohio]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalConsolidationWith
Context triple: [Osborn, Ohio, municipalConsolidationWith, Fairborn, Ohio]
  • A. hasMunicipalConsolidationWith chosen
    Indicates that two or more municipalities have been officially merged or unified into a single administrative entity or structure.
  • B. municipalIntegration
    Indicates the incorporation or coordination of local governmental functions, services, or jurisdictions into a unified municipal framework.
  • C. municipalityReform
    Indicates a formal reorganization or restructuring of a municipality’s administrative boundaries, governance, or status.
  • D. formedMunicipalityWith
    Indicates that two or more entities combined or were merged to create a single municipality.
  • E. allowsMunicipalitiesTo
    Indicates that an entity grants municipalities the authority, permission, or legal capacity to perform a specified action or exercise a particular power.
  • F. None of above.

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_69f0a7a180e48190ae775e40047dbcb5 completed April 28, 2026, 12:27 p.m.
NER Named-entity recognition batch_69f6a8df16a88190a23820e64a3b1f92 completed May 3, 2026, 1:46 a.m.
PD Predicate disambiguation batch_69f6a751d5e48190a77dcecbe7ef9f0b completed May 3, 2026, 1:39 a.m.
Created at: April 28, 2026, 3:17 p.m.