Triple

T29583301
Position Surface form Disambiguated ID Type / Status
Subject Sequim Valley Airport E753649 entity
Predicate locatedNear P294 FINISHED
Object Sequim Bay
Sequim Bay is a sheltered inlet on the northeastern coast of Washington’s Olympic Peninsula, known for its calm waters, shellfish beds, and proximity to the town of Sequim.
E1894386 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: Sequim Bay | Statement: [Sequim Valley Airport, locatedNear, Sequim Bay]
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: Sequim Bay
Triple: [Sequim Valley Airport, locatedNear, Sequim Bay]
Generated description
Sequim Bay is a sheltered inlet on the northeastern coast of Washington’s Olympic Peninsula, known for its calm waters, shellfish beds, and proximity to the town of Sequim.

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_69f0ef80bf8c8190ad286e99f7df0c63 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66d7b547c8190ba4bfef5c7567a77 completed May 2, 2026, 9:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721d442b0819087f07e25f18a922b completed June 8, 2026, 8:11 p.m.
NEDg Description generation batch_6a2723656f888190b66e470c94c4e03f completed June 8, 2026, 8:17 p.m.
NED2 Entity disambiguation (via description) batch_6a2723e6c6648190801fec9c9fd7f557 completed June 8, 2026, 8:19 p.m.
Created at: April 28, 2026, 6:08 p.m.