Triple

T8995612
Position Surface form Disambiguated ID Type / Status
Subject Poestenkill, New York E214897 entity
Predicate roadAccess P385 FINISHED
Object New York State Route 355
New York State Route 355 is a short state highway in Rensselaer County, New York, connecting rural communities near Poestenkill to the regional road network.
E2296958 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 York State Route 355 | Statement: [Poestenkill, New York, roadAccess, New York State Route 355]
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 York State Route 355
Triple: [Poestenkill, New York, roadAccess, New York State Route 355]
Generated description
New York State Route 355 is a short state highway in Rensselaer County, New York, connecting rural communities near Poestenkill to the regional road network.

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_69ca83a05c608190bdfdbdb25e994b39 completed March 30, 2026, 2:07 p.m.
NER Named-entity recognition batch_69cc68df33c48190a5017426e59c0bc4 completed April 1, 2026, 12:37 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82e667feb0819085165db53e409d0b completed Aug. 17, 2026, 10:46 a.m.
NEDg Description generation batch_6a82e6dcf6ec8190b056a64dc36f1a9d completed Aug. 17, 2026, 10:47 a.m.
NED2 Entity disambiguation (via description) batch_6a82e8e68c7c8190963b6ee00a4fca9b completed Aug. 17, 2026, 10:56 a.m.
Created at: March 30, 2026, 7:04 p.m.