Triple

T29796730
Position Surface form Disambiguated ID Type / Status
Subject Yellow Spring, West Virginia E756571 entity
Predicate locatedInU.S._county P23957 FINISHED
Object Hampshire County, West Virginia 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: Hampshire County, West Virginia | Statement: [Yellow Spring, West Virginia, locatedInU.S._county, Hampshire County, West Virginia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: locatedInU.S._county
Context triple: [Yellow Spring, West Virginia, locatedInU.S._county, Hampshire County, West Virginia]
  • A. locatedInCountySeatOfCounty
    Indicates that one entity is located in the county seat city or town of the specified county.
  • B. locatedInCountyRegion
    Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
  • C. inCounty chosen
    Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
  • D. isNamedCountyOf
    Indicates that a county bears a specific official name within a given jurisdiction or context.
  • E. isInCountySeatOf
    Indicates that one entity is located within the town or city that serves as the administrative center (county seat) of a specified county.
  • 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_69f22454583081908927516cb9938d1d completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_6a005b2e0a9c819081c6f7ccbef49ff8 completed May 10, 2026, 10:17 a.m.
PD Predicate disambiguation batch_6a005a8bcde88190ace2bc0215e26430 completed May 10, 2026, 10:14 a.m.
Created at: April 29, 2026, 5:15 p.m.