Triple

T37751441
Position Surface form Disambiguated ID Type / Status
Subject Somerset County highway system E940991 entity
Predicate hasComponent P35 FINISHED
Object Somerset County Route 639
Somerset County Route 639 is a county-maintained roadway in Somerset County, New Jersey, serving local and regional traffic within the county’s highway network.
E2284429 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: Somerset County Route 639 | Statement: [Somerset County highway system, hasComponent, Somerset County Route 639]
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: Somerset County Route 639
Triple: [Somerset County highway system, hasComponent, Somerset County Route 639]
Generated description
Somerset County Route 639 is a county-maintained roadway in Somerset County, New Jersey, serving local and regional traffic within the county’s highway 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_69f76ee1f3a88190834e6c8af99bccc9 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaef0cec881908c2742d77d145901 completed May 6, 2026, 9:13 p.m.
NED1 Entity disambiguation (via context triple) batch_6a438a29b9948190ba3fec2d82327fe9 completed June 30, 2026, 9:19 a.m.
NEDg Description generation batch_6a438b34d0248190b026f09b127d17cf completed June 30, 2026, 9:24 a.m.
NED2 Entity disambiguation (via description) batch_6a438bfd9c008190b69f2f8809afd0a4 completed June 30, 2026, 9:27 a.m.
Created at: May 3, 2026, 4:19 p.m.