Triple

T37604673
Position Surface form Disambiguated ID Type / Status
Subject National Historic Landmarks in Ohio E935614 entity
Predicate relationshipToNRHP GENERATED
Object subset of properties listed on the National Register of Historic Places UNRECOGNIZED GENERATED

How this triple was built (1 step)

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.

PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: relationshipToNRHP
Context triple: [National Historic Landmarks in Ohio, relationshipToNRHP, subset of properties listed on the National Register of Historic Places]
  • A. relationshipToNationalTreasures
    Indicates a specified type of connection or association that an entity has with designated national treasures.
  • B. NRHPContributingPropertyTo
    Indicates that a property is recognized as a contributing element to a larger site or district listed on the National Register of Historic Places (NRHP).
  • C. notableArchitectureRelation
    Indicates a relationship where one entity is recognized as a significant or noteworthy example of architecture in connection to another entity.
  • D. NRHPReference
    Indicates that an entity is associated with a specific reference entry or identifier in the National Register of Historic Places.
  • E. hasWorkOnTheNationalRegisterOfHistoricPlaces
    Indicates that an entity has created, contributed to, or is otherwise associated with a work that is listed on the National Register of Historic Places.
  • F. None of above. chosen

Provenance (1 batch)

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_69f76ed0a85481909254a8a89090c826 completed May 3, 2026, 3:50 p.m.
Created at: May 3, 2026, 4:18 p.m.