Triple

T20588731
Position Surface form Disambiguated ID Type / Status
Subject Maryland Route 118 E505856 entity
Predicate connectsTo P845 FINISHED
Object Middlebrook Road
Middlebrook Road is a major local thoroughfare in Montgomery County, Maryland, serving residential, commercial, and institutional areas and intersecting key state routes.
E2114937 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: Middlebrook Road | Statement: [Maryland Route 118, connectsTo, Middlebrook Road]
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: Middlebrook Road
Triple: [Maryland Route 118, connectsTo, Middlebrook Road]
Generated description
Middlebrook Road is a major local thoroughfare in Montgomery County, Maryland, serving residential, commercial, and institutional areas and intersecting key 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_69e0b4b9669c8190b8e81fc72817d42c completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a9790cc08190b48949834cd421d2 completed April 20, 2026, 10:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37792448c88190ba18544f9ca011e3 completed June 21, 2026, 5:39 a.m.
NEDg Description generation batch_6a377a6cd7c48190aa8d76a19cd6ef4e completed June 21, 2026, 5:45 a.m.
NED2 Entity disambiguation (via description) batch_6a377b124f288190a861cdacfbbc0b5d completed June 21, 2026, 5:48 a.m.
Created at: April 16, 2026, 11:40 a.m.