Triple

T8172825
Position Surface form Disambiguated ID Type / Status
Subject Buckland, Virginia E190863 entity
Predicate hasNRHPReferenceNumber P2954 FINISHED
Object 74002148 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: 74002148 | Statement: [Buckland, Virginia, hasNRHPReferenceNumber, 74002148]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNRHPReferenceNumber
Context triple: [Buckland, Virginia, hasNRHPReferenceNumber, 74002148]
  • A. NRHPReferenceNumber chosen
    Indicates the unique identification number assigned to a property or site listed in the National Register of Historic Places.
  • B. NRHPReference
    Indicates that an entity is associated with a specific reference entry or identifier in the National Register of Historic Places.
  • C. hasNotableHistoricalAssociation
    Indicates that there is a significant connection between an entity and an important historical event, figure, period, or development.
  • D. locatedInNationalHistoricalPark
    Indicates that something is situated within the boundaries of a designated national historical park.
  • E. designatedNationalHistoricLandmark
    Indicates that an entity has been officially recognized and assigned status as a national historic landmark by the appropriate authority.
  • 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_69ca82c1c0a08190bf8692b4d91a03ca completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb4807c9808190ad91a9c688a4c7fd completed March 31, 2026, 4:05 a.m.
PD Predicate disambiguation batch_69cb36a4c40c81909f60aef0e1624c13 completed March 31, 2026, 2:51 a.m.
Created at: March 30, 2026, 5:39 p.m.