Triple
T20938018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gerzensee |
E515636
|
entity |
| Predicate | hasLakeSurfaceType |
P79996
|
FINISHED |
| Object | natural lake |
—
|
LITERAL 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: natural lake | Statement: [Gerzensee, hasLakeSurfaceType, natural lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLakeSurfaceType Context triple: [Gerzensee, hasLakeSurfaceType, natural lake]
-
A.
isLakeType
chosen
Indicates that one entity is a specific type or category of lake in relation to another entity.
-
B.
hasLakeThatRepresents
Indicates a relationship where a lake serves as a symbolic or representative feature for something, such as a place, concept, or entity.
-
C.
isInLake
Indicates that one entity is located within the body of water defined as a lake.
-
D.
hasLakes
Indicates that one entity possesses, contains, or is characterized by the presence of one or more lakes.
-
E.
isHighAltitudeLake
Indicates that a lake is situated at a relatively high elevation above sea level.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9534cd48190a86665fb1df6b077 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:50 p.m.