Triple

T28055851
Position Surface form Disambiguated ID Type / Status
Subject Nisqually Corridor of Mount Rainier National Park E708964 entity
Predicate accessedVia P1985 FINISHED
Object State Route 706
State Route 706 is a Washington state highway that serves as the primary western access road to Mount Rainier National Park.
E2294333 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 706 | Statement: [Nisqually Corridor of Mount Rainier National Park, accessedVia, State Route 706]
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 706
Triple: [Nisqually Corridor of Mount Rainier National Park, accessedVia, State Route 706]
Generated description
State Route 706 is a Washington state highway that serves as the primary western access road to Mount Rainier National Park.

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_69ef9b6df9f48190bbb971d02cbe1b65 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f63fdcaf288190b0b5118b835b940b completed May 2, 2026, 6:18 p.m.
NED1 Entity disambiguation (via context triple) batch_6a7bd62cfbc88190ac83347f5f530f44 completed Aug. 12, 2026, 2:10 a.m.
NEDg Description generation batch_6a7bd77536a08190a603b7ee2c31e28f completed Aug. 12, 2026, 2:16 a.m.
NED2 Entity disambiguation (via description) batch_6a7bd7d0da048190b10b93b5e3a6b86e completed Aug. 12, 2026, 2:17 a.m.
Created at: April 27, 2026, 8:36 p.m.