Triple

T24442095
Position Surface form Disambiguated ID Type / Status
Subject Loudon, New Hampshire E616291 entity
Predicate hasMajorRoad P385 FINISHED
Object New Hampshire Route 129
New Hampshire Route 129 is a state highway in central New Hampshire that serves as a local connector route through the town of Loudon and surrounding communities.
E1787798 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: New Hampshire Route 129 | Statement: [Loudon, New Hampshire, hasMajorRoad, New Hampshire Route 129]
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: New Hampshire Route 129
Triple: [Loudon, New Hampshire, hasMajorRoad, New Hampshire Route 129]
Generated description
New Hampshire Route 129 is a state highway in central New Hampshire that serves as a local connector route through the town of Loudon and surrounding communities.

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_69e2d7ec44b081909ccaf1f3bbec0641 completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f2985129cc8190b5c99747d2dbcac8 completed April 29, 2026, 11:46 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12ec8329f08190b6b41160368b7a44 completed May 24, 2026, 12:18 p.m.
NEDg Description generation batch_6a12ed2afa9481909cc0ca56270ba2a0 completed May 24, 2026, 12:20 p.m.
NED2 Entity disambiguation (via description) batch_6a12edccfe54819094da363072bdf7a6 completed May 24, 2026, 12:23 p.m.
Created at: April 18, 2026, 2:17 a.m.