Triple

T34590691
Position Surface form Disambiguated ID Type / Status
Subject Kernstown, Virginia E888172 entity
Predicate hasTransportationRoute P385 FINISHED
Object Valley Pike
Valley Pike is a historic roadway in Virginia’s Shenandoah Valley that served as a key transportation and military route, especially during the American Civil War.
E2296257 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: Valley Pike | Statement: [Kernstown, Virginia, hasTransportationRoute, Valley Pike]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Valley Pike
Triple: [Kernstown, Virginia, hasTransportationRoute, Valley Pike]
Generated description
Valley Pike is a historic roadway in Virginia’s Shenandoah Valley that served as a key transportation and military route, especially during the American Civil War.

Provenance (5 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_69f349d3bfcc81909874c99e646fb3ea completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f72158f7c081909aed6ea12089998c completed May 3, 2026, 10:20 a.m.
NED1 Entity disambiguation (via context triple) batch_6a8254f9ae248190a370c9cb15d1bd01 completed Aug. 17, 2026, 12:25 a.m.
NEDg Description generation batch_6a82551f906c8190bc2509f4b4451f31 completed Aug. 17, 2026, 12:26 a.m.
NED2 Entity disambiguation (via description) batch_6a825571ad0081908ad631d65cb7dd1d completed Aug. 17, 2026, 12:27 a.m.
Created at: May 1, 2026, 2:03 a.m.