Triple

T23292985
Position Surface form Disambiguated ID Type / Status
Subject Connecticut Route 66 E590083 entity
Predicate isNumberedAfter P4527 FINISHED
Object Connecticut Route 65
Connecticut Route 65 is a former state highway in Connecticut that once served as a regional connector route before being renumbered and incorporated into other state routes.
E1814284 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: Connecticut Route 65 | Statement: [Connecticut Route 66, isNumberedAfter, Connecticut Route 65]
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: Connecticut Route 65
Triple: [Connecticut Route 66, isNumberedAfter, Connecticut Route 65]
Generated description
Connecticut Route 65 is a former state highway in Connecticut that once served as a regional connector route before being renumbered and incorporated into other state routes.

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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196ccd9b481909ab5d3504640025e completed April 29, 2026, 5:27 a.m.
NED1 Entity disambiguation (via context triple) batch_6a16277bde7c8190b0c7763b41f34773 completed May 26, 2026, 11:06 p.m.
NEDg Description generation batch_6a1628bdc5ac81909d5f7dbdfad7934c completed May 26, 2026, 11:11 p.m.
NED2 Entity disambiguation (via description) batch_6a16294f42508190aac4e3617131dafe completed May 26, 2026, 11:14 p.m.
Created at: April 17, 2026, 5:02 p.m.