Triple

T20789097
Position Surface form Disambiguated ID Type / Status
Subject Duboce Triangle E511721 entity
Predicate namedAfter P63 FINISHED
Object Duboce Avenue
Duboce Avenue is a street in San Francisco, California, known for running along the northern edge of the Duboce Triangle neighborhood and serving as a key local thoroughfare.
E1763144 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: Duboce Avenue | Statement: [Duboce Triangle, namedAfter, Duboce Avenue]
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: Duboce Avenue
Triple: [Duboce Triangle, namedAfter, Duboce Avenue]
Generated description
Duboce Avenue is a street in San Francisco, California, known for running along the northern edge of the Duboce Triangle neighborhood and serving as a key local thoroughfare.

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_69e0b4cb83948190bd57bec21d78ed53 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6c28dfb8c8190a10289c157a61c67 completed April 21, 2026, 12:19 a.m.
NED1 Entity disambiguation (via context triple) batch_6a126239807881908843eaced3181240 completed May 24, 2026, 2:28 a.m.
NEDg Description generation batch_6a12667d95ec8190900555e50d903e5d completed May 24, 2026, 2:46 a.m.
NED2 Entity disambiguation (via description) batch_6a1266dd3b748190a06a76a7587eff99 completed May 24, 2026, 2:47 a.m.
Created at: April 16, 2026, 12:38 p.m.