Triple

T36466060
Position Surface form Disambiguated ID Type / Status
Subject Milk Street (Boston) E898424 entity
Predicate connectsTo P845 FINISHED
Object India Street (Boston)
India Street is a short historic street in downtown Boston, Massachusetts, located in the Financial District near other colonial-era streets.
E2187842 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: India Street (Boston) | Statement: [Milk Street (Boston), connectsTo, India Street (Boston)]
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: India Street (Boston)
Triple: [Milk Street (Boston), connectsTo, India Street (Boston)]
Generated description
India Street is a short historic street in downtown Boston, Massachusetts, located in the Financial District near other colonial-era streets.

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_69f76e58ebd88190b75d9b169b59d793 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bdb5ba988190970ecf921394e2cc completed May 3, 2026, 9:27 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39dbc635f48190988b21749b525191 completed June 23, 2026, 1:05 a.m.
NEDg Description generation batch_6a39dcf1719c81908ea09bfb7b3d933e completed June 23, 2026, 1:10 a.m.
NED2 Entity disambiguation (via description) batch_6a39e11747f88190bf623eb195127d87 completed June 23, 2026, 1:27 a.m.
Created at: May 3, 2026, 4:10 p.m.