Triple

T29622531
Position Surface form Disambiguated ID Type / Status
Subject Bradley Boulevard E755037 entity
Predicate officialName P66 FINISHED
Object Maryland Route 191
Maryland Route 191 is a state highway in Montgomery County, Maryland, running primarily along Bradley Boulevard and serving suburban communities near Washington, D.C.
E2077320 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: Maryland Route 191 | Statement: [Bradley Boulevard, officialName, Maryland Route 191]
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: Maryland Route 191
Triple: [Bradley Boulevard, officialName, Maryland Route 191]
Generated description
Maryland Route 191 is a state highway in Montgomery County, Maryland, running primarily along Bradley Boulevard and serving suburban communities near Washington, D.C.

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_69f0ef86b6ec8190a87fff07fd983b1e completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66e263460819086f937487b3187b2 completed May 2, 2026, 9:35 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3692b39e588190b14d5899cbdb08b1 completed June 20, 2026, 1:16 p.m.
NEDg Description generation batch_6a3693978aa881909be8384c3d62bc33 completed June 20, 2026, 1:20 p.m.
NED2 Entity disambiguation (via description) batch_6a3694b83d048190a29c179e9407f41f completed June 20, 2026, 1:25 p.m.
Created at: April 28, 2026, 6:35 p.m.