Triple

T24063596
Position Surface form Disambiguated ID Type / Status
Subject Aurora Avenue North E596023 entity
Predicate hasJunctionWith P1018 FINISHED
Object North 145th Street
North 145th Street is a major east–west arterial road in the Seattle area that serves as a key boundary and connector between neighborhoods and highways.
E1628639 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: North 145th Street | Statement: [Aurora Avenue North, hasJunctionWith, North 145th 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: North 145th Street
Triple: [Aurora Avenue North, hasJunctionWith, North 145th Street]
Generated description
North 145th Street is a major east–west arterial road in the Seattle area that serves as a key boundary and connector between neighborhoods and highways.

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_69e288c25c008190850cf447940ab181 completed April 17, 2026, 7:23 p.m.
NER Named-entity recognition batch_69f1da598dec8190a625309fd8f10f1d completed April 29, 2026, 10:15 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0fc99c2e5c8190a713432e5792931b completed May 22, 2026, 3:12 a.m.
NEDg Description generation batch_6a0fcccff9e88190a98d2037d4e781fc completed May 22, 2026, 3:26 a.m.
NED2 Entity disambiguation (via description) batch_6a0fcd80ae2c81909ab307688454443b completed May 22, 2026, 3:29 a.m.
Created at: April 17, 2026, 10:39 p.m.