Triple

T24198538
Position Surface form Disambiguated ID Type / Status
Subject Durango Drive E599901 entity
Predicate crosses P416 FINISHED
Object Lake Mead Boulevard
Lake Mead Boulevard is a major east–west arterial road in the Las Vegas Valley, Nevada, serving residential, commercial, and commuter traffic across multiple neighborhoods.
E1635230 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: Lake Mead Boulevard | Statement: [Durango Drive, crosses, Lake Mead Boulevard]
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: Lake Mead Boulevard
Triple: [Durango Drive, crosses, Lake Mead Boulevard]
Generated description
Lake Mead Boulevard is a major east–west arterial road in the Las Vegas Valley, Nevada, serving residential, commercial, and commuter traffic across multiple neighborhoods.

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_69e288ceaab88190899d0acb5931591d completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f27c9ddfcc819096697a844b300cce completed April 29, 2026, 9:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a0fe3415db88190830fd5abdf002f89 completed May 22, 2026, 5:01 a.m.
NEDg Description generation batch_6a0fe4f9f0448190bbd9e0b860335482 completed May 22, 2026, 5:09 a.m.
NED2 Entity disambiguation (via description) batch_6a0fe620e40c81909973369ffb8e9dfc completed May 22, 2026, 5:14 a.m.
Created at: April 17, 2026, 11:36 p.m.