Triple

T15177602
Position Surface form Disambiguated ID Type / Status
Subject Mackenzie, British Columbia E362650 entity
Predicate hasNearbyAttraction P2064 FINISHED
Object Morfee Lake
Morfee Lake is a scenic recreational lake near Mackenzie in northern British Columbia, popular for activities such as swimming, boating, and fishing.
E1930180 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: Morfee Lake | Statement: [Mackenzie, British Columbia, hasNearbyAttraction, Morfee Lake]
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: Morfee Lake
Triple: [Mackenzie, British Columbia, hasNearbyAttraction, Morfee Lake]
Generated description
Morfee Lake is a scenic recreational lake near Mackenzie in northern British Columbia, popular for activities such as swimming, boating, and fishing.

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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e00663b4148190b647592eda315d1d completed April 15, 2026, 9:42 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28b06199e48190a1da91f03a6f8712 completed June 10, 2026, 12:31 a.m.
NEDg Description generation batch_6a28b1b3d41481908b42370b7ad16ba4 completed June 10, 2026, 12:37 a.m.
NED2 Entity disambiguation (via description) batch_6a28b2561d808190b5fbfc96e46634df completed June 10, 2026, 12:39 a.m.
Created at: April 10, 2026, 3:09 a.m.