Triple

T6843574
Position Surface form Disambiguated ID Type / Status
Subject Harrisonburg, Virginia E157835 entity
Predicate hasNickname P39 FINISHED
Object Rocktown E622803 NE 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: Rocktown | Statement: [Harrisonburg, Virginia, hasNickname, Rocktown]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rocktown
Context triple: [Harrisonburg, Virginia, hasNickname, Rocktown]
  • A. Rocktown chosen
    Rocktown was the original name of what is now Harrisonburg, Virginia, a city in the Shenandoah Valley.
  • B. Longtown
    Longtown is a small town in Cumbria, England, situated near the Scottish border and historically associated with the county of Cumberland.
  • C. Darbyville
    Darbyville is the former name of the city now known as Macclenny in Baker County, Florida.
  • D. Shingletown
    Shingletown is a small rural community in Northern California known for its forested setting near Lassen Volcanic National Park.
  • E. Martintown
    Martintown is a small rural community located within the Township of South Glengarry in eastern Ontario, Canada.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69c6882ed4c081909dc465a7cf8838be completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d6b7179481909e3482fef47b2719 completed March 27, 2026, 7:12 p.m.
NED1 Entity disambiguation (via context triple) batch_69c74271b9dc8190abbe3b1f9819c38f completed March 28, 2026, 2:52 a.m.
Created at: March 27, 2026, 2:19 p.m.