Triple

T8337479
Position Surface form Disambiguated ID Type / Status
Subject Miamisburg, Ohio E195823 entity
Predicate hasHistoricBuildingStock P42084 FINISHED
Object 19th-century commercial buildings LITERAL 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: 19th-century commercial buildings | Statement: [Miamisburg, Ohio, hasHistoricBuildingStock, 19th-century commercial buildings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasHistoricBuildingStock
Context triple: [Miamisburg, Ohio, hasHistoricBuildingStock, 19th-century commercial buildings]
  • A. hasPreservedBuildings chosen
    Indicates that an entity possesses buildings that have been maintained or kept in their original or historical condition.
  • B. hasHistoricChurches
    Indicates that an entity possesses or contains one or more churches of recognized historical significance.
  • C. residenceHistoric
    Indicates that a residence has historical significance or is formally recognized as a historic dwelling.
  • D. hasHistoricDistrict
    Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
  • E. hasHistoricSite
    Indicates that an entity possesses, contains, or is associated with a place recognized for its historical significance.
  • 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_69ca82ecbdc481908a55cad8ca062d88 completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7fd5027c81909724f25aa30bbe58 completed March 31, 2026, 8:03 a.m.
PD Predicate disambiguation batch_69cb70c3231c81909e3d463192c9de22 completed March 31, 2026, 6:59 a.m.
Created at: March 30, 2026, 5:57 p.m.