Triple

T34510509
Position Surface form Disambiguated ID Type / Status
Subject U.S. Route 101 in Mountain View E886004 entity
Predicate hasJunctionWith P1018 FINISHED
Object Rengstorff Avenue
Rengstorff Avenue is a major north–south arterial road in Mountain View, California, connecting residential neighborhoods, commercial areas, and key regional routes.
E2296759 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: Rengstorff Avenue | Statement: [U.S. Route 101 in Mountain View, hasJunctionWith, Rengstorff 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: Rengstorff Avenue
Triple: [U.S. Route 101 in Mountain View, hasJunctionWith, Rengstorff Avenue]
Generated description
Rengstorff Avenue is a major north–south arterial road in Mountain View, California, connecting residential neighborhoods, commercial areas, and key regional routes.

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_69f349cc0220819081f154c6964f4dc2 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f71f9026f481909b425988ec1e99db completed May 3, 2026, 10:12 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82b2fa00f881909c7aeba853dbd06d completed Aug. 17, 2026, 7:06 a.m.
NEDg Description generation batch_6a82b3f2c878819083ed2b8f31b40a08 completed Aug. 17, 2026, 7:10 a.m.
NED2 Entity disambiguation (via description) batch_6a82b444948c8190bc4b1f2ba7548051 completed Aug. 17, 2026, 7:12 a.m.
Created at: May 1, 2026, 2:01 a.m.