Triple

T9482597
Position Surface form Disambiguated ID Type / Status
Subject Uphams Corner E228679 entity
Predicate hasMajorStreet P30026 FINISHED
Object Dudley Street
Dudley Street is a major thoroughfare in Boston, Massachusetts, running through neighborhoods such as Uphams Corner and serving as an important local commercial and residential corridor.
E2295830 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: Dudley Street | Statement: [Uphams Corner, hasMajorStreet, Dudley Street]
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: Dudley Street
Triple: [Uphams Corner, hasMajorStreet, Dudley Street]
Generated description
Dudley Street is a major thoroughfare in Boston, Massachusetts, running through neighborhoods such as Uphams Corner and serving as an important local commercial and residential corridor.

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_69ca84730a5081908de282651019bf2f completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd804af6d08190a281cb27407c791c completed April 1, 2026, 8:30 p.m.
NED1 Entity disambiguation (via context triple) batch_6a81fadc9570819082575d8ed6c92fb1 completed Aug. 16, 2026, 6:01 p.m.
NEDg Description generation batch_6a81fb373fa08190b92de8beb0d189c1 completed Aug. 16, 2026, 6:02 p.m.
NED2 Entity disambiguation (via description) batch_6a81fb8a3dc48190b3f66fd6be7b14fa completed Aug. 16, 2026, 6:03 p.m.
Created at: March 30, 2026, 7:55 p.m.