Triple

T18439634
Position Surface form Disambiguated ID Type / Status
Subject 3rd Avenue (Seattle) E450491 entity
Predicate connectsTo P845 FINISHED
Object Cherry Street
Cherry Street is a major east–west thoroughfare in downtown Seattle, Washington, running through the city’s central business district and connecting key north–south avenues.
E1747878 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: Cherry Street | Statement: [3rd Avenue (Seattle), connectsTo, Cherry 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: Cherry Street
Triple: [3rd Avenue (Seattle), connectsTo, Cherry Street]
Generated description
Cherry Street is a major east–west thoroughfare in downtown Seattle, Washington, running through the city’s central business district and connecting key north–south avenues.

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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0fda908190901a108fb9982a2d completed April 19, 2026, 6:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a121e64ef3081908b39a3c83e4440f3 completed May 23, 2026, 9:38 p.m.
NEDg Description generation batch_6a121fa58ae08190b70faa7e3c81eae8 completed May 23, 2026, 9:44 p.m.
NED2 Entity disambiguation (via description) batch_6a1220284ddc819085b3ca2cad3fbfa9 completed May 23, 2026, 9:46 p.m.
Created at: April 10, 2026, 11:30 a.m.