Triple
T25313491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarner Aa |
E634667
|
entity |
| Predicate | hasMajorLakeAlongCourse |
P98023
|
FINISHED |
| Object | Lake Sarnen |
—
|
NE NERFINISHED |
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: Lake Sarnen | Statement: [Sarner Aa, hasMajorLakeAlongCourse, Lake Sarnen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorLakeAlongCourse Context triple: [Sarner Aa, hasMajorLakeAlongCourse, Lake Sarnen]
-
A.
hasLakeOnCourse
chosen
Indicates that a course (such as a route or path) includes at least one lake situated along its way or within its boundaries.
-
B.
hasMajorLake
Indicates that a geographic region or area contains at least one significant lake within its boundaries.
-
C.
hasMajorLakeAtSource
Indicates that the source of a river or stream is located in, or directly associated with, a major lake.
-
D.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
-
E.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
- F. None of above.
Provenance (3 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 21, 2026, 1:27 p.m.