Triple

T27198482
Position Surface form Disambiguated ID Type / Status
Subject Kluane Lake E683669 entity
Predicate nearestSettlement P3883 FINISHED
Object Destruction Bay
Destruction Bay is a small community in Yukon, Canada, located along the Alaska Highway on the shore of Kluane Lake and serving as a service and tourism stop in the region.
E1759737 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: Destruction Bay | Statement: [Kluane Lake, nearestSettlement, Destruction 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: Destruction Bay
Triple: [Kluane Lake, nearestSettlement, Destruction Bay]
Generated description
Destruction Bay is a small community in Yukon, Canada, located along the Alaska Highway on the shore of Kluane Lake and serving as a service and tourism stop in the 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_69eefad1fd5c8190a4a46ea6afe58bfa completed April 27, 2026, 5:57 a.m.
NER Named-entity recognition batch_69f625b229f08190ae2517727533105d completed May 2, 2026, 4:26 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12539b6a3881909f8c4b10b4ac9cba completed May 24, 2026, 1:25 a.m.
NEDg Description generation batch_6a125433c0288190ab1e54c3d763468d completed May 24, 2026, 1:28 a.m.
NED2 Entity disambiguation (via description) batch_6a1254f46d288190aa6f45f8c8e9007d completed May 24, 2026, 1:31 a.m.
Created at: April 27, 2026, 9:35 a.m.