Triple

T32743283
Position Surface form Disambiguated ID Type / Status
Subject Princess Anne, Maryland E837282 entity
Predicate servedByHighway P385 FINISHED
Object Maryland Route 675
Maryland Route 675 is a short state highway in Somerset County that serves as a local connector through the town of Princess Anne, paralleling U.S. Route 13.
E2147608 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 675 | Statement: [Princess Anne, Maryland, servedByHighway, Maryland Route 675]
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 675
Triple: [Princess Anne, Maryland, servedByHighway, Maryland Route 675]
Generated description
Maryland Route 675 is a short state highway in Somerset County that serves as a local connector through the town of Princess Anne, paralleling U.S. Route 13.

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_69f34936e1748190b797e406e4e9293a completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6cc1c33048190a17142b6c4d12470 completed May 3, 2026, 4:16 a.m.
NED1 Entity disambiguation (via context triple) batch_6a385bb22d0c8190a2fbb1d8f570d805 completed June 21, 2026, 9:46 p.m.
NEDg Description generation batch_6a385cfee66c8190a546393089b8d789 completed June 21, 2026, 9:51 p.m.
NED2 Entity disambiguation (via description) batch_6a385df5220881908ae1a6c6e999e3fa completed June 21, 2026, 9:56 p.m.
Created at: May 1, 2026, 1:12 a.m.