Triple

T36873032
Position Surface form Disambiguated ID Type / Status
Subject Lake Vanajavesi E911270 entity
Predicate hasNearbyFeature P350 FINISHED
Object Aulanko ridge
Aulanko ridge is a scenic esker formation in Hämeenlinna, Finland, known for its forested landscapes, viewpoints, and role as a popular nature and recreation area.
E2203387 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: Aulanko ridge | Statement: [Lake Vanajavesi, hasNearbyFeature, Aulanko ridge]
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: Aulanko ridge
Triple: [Lake Vanajavesi, hasNearbyFeature, Aulanko ridge]
Generated description
Aulanko ridge is a scenic esker formation in Hämeenlinna, Finland, known for its forested landscapes, viewpoints, and role as a popular nature and recreation area.

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_69f76e82339881909607a65c0503d941 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cff4e3ac8190bf2dcc45a7890ea8 completed May 3, 2026, 10:45 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3dfae7e8548190a2b68510a30b7fd5 completed June 26, 2026, 4:07 a.m.
NEDg Description generation batch_6a3e0194f264819083992f99329f098b completed June 26, 2026, 4:35 a.m.
NED2 Entity disambiguation (via description) batch_6a3e06fa82348190bfe91700321babed completed June 26, 2026, 4:58 a.m.
Created at: May 3, 2026, 4:13 p.m.