Triple

T7508882
Position Surface form Disambiguated ID Type / Status
Subject LoDo, Denver E177462 entity
Predicate hasStreet P959 FINISHED
Object Blake Street
Blake Street is a historic thoroughfare running through Denver’s Lower Downtown (LoDo) district, known for its renovated brick warehouses, bars, restaurants, and proximity to Coors Field.
E2293672 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: Blake Street | Statement: [LoDo, Denver, hasStreet, Blake 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: Blake Street
Triple: [LoDo, Denver, hasStreet, Blake Street]
Generated description
Blake Street is a historic thoroughfare running through Denver’s Lower Downtown (LoDo) district, known for its renovated brick warehouses, bars, restaurants, and proximity to Coors Field.

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_69c69f276b108190af2cc790b6554544 completed March 27, 2026, 3:15 p.m.
NER Named-entity recognition batch_69c6f5d052888190ae8678f9134d737c completed March 27, 2026, 9:25 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7aeded27f88190a53f0bcd6ef78958 completed Aug. 11, 2026, 9:39 a.m.
NEDg Description generation batch_6a7aee8722b48190937dbed11e16272e completed Aug. 11, 2026, 9:42 a.m.
NED2 Entity disambiguation (via description) batch_6a7aeef6652c8190a528fe461a9a8382 completed Aug. 11, 2026, 9:44 a.m.
Created at: March 27, 2026, 3:45 p.m.