Triple

T32943596
Position Surface form Disambiguated ID Type / Status
Subject Noisy-Diobsud Wilderness E842737 entity
Predicate contains P35 FINISHED
Object Noisy Creek
Noisy Creek is a stream located within the Noisy-Diobsud Wilderness area of Washington State’s North Cascades region.
E2296551 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: Noisy Creek | Statement: [Noisy-Diobsud Wilderness, contains, Noisy Creek]
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: Noisy Creek
Triple: [Noisy-Diobsud Wilderness, contains, Noisy Creek]
Generated description
Noisy Creek is a stream located within the Noisy-Diobsud Wilderness area of Washington State’s North Cascades region.

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_69f34949727c81909d195c97de3341c8 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6d13e418481909ddd7adecf52255f completed May 3, 2026, 4:38 a.m.
NED1 Entity disambiguation (via context triple) batch_6a82893f98ec8190a5d598c84c5e5c31 completed Aug. 17, 2026, 4:08 a.m.
NEDg Description generation batch_6a828a3932788190bae2a1bcf568f6af completed Aug. 17, 2026, 4:12 a.m.
NED2 Entity disambiguation (via description) batch_6a828a8c344c81909cd0b49627ad2ebe completed Aug. 17, 2026, 4:14 a.m.
Created at: May 1, 2026, 1:20 a.m.