Triple

T21394211
Position Surface form Disambiguated ID Type / Status
Subject Issaquah, Washington E527736 entity
Predicate hasMajorRoad P385 FINISHED
Object State Route 900
State Route 900 is a state highway in Washington that connects the city of Issaquah with the Seattle metropolitan area, serving as a key east–west commuter and regional traffic corridor.
 E2287687 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: State Route 900 | Statement: [Issaquah, Washington, hasMajorRoad, State Route 900]
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: State Route 900
Triple: [Issaquah, Washington, hasMajorRoad, State Route 900]
Generated description
State Route 900 is a state highway in Washington that connects the city of Issaquah with the Seattle metropolitan area, serving as a key east–west commuter and regional traffic corridor.

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_69e0b51ff3748190935c0a513c62a12b completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69ee62cd30f08190aba90afed6116a2a completed April 26, 2026, 7:09 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5a0c4d2de481908487bdaa2fdcbd72 completed July 17, 2026, 11:04 a.m.
NEDg Description generation batch_6a5a0d2b49108190977dc434f63f20b3 completed July 17, 2026, 11:08 a.m.
NED2 Entity disambiguation (via description) batch_6a5a0e18fc7c8190b84670454596f9d7 completed July 17, 2026, 11:12 a.m.
Created at: April 16, 2026, 5:13 p.m.