Triple
T10587385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake of Gruyère |
E249888
|
entity |
| Predicate | waterSurfaceElevation |
P47800
|
FINISHED |
| Object | 677 metres above sea level |
—
|
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: 677 metres above sea level | Statement: [Lake of Gruyère, waterSurfaceElevation, 677 metres above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterSurfaceElevation Context triple: [Lake of Gruyère, waterSurfaceElevation, 677 metres above sea level]
-
A.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
B.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
C.
reservoirElevation
chosen
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
D.
surfaceWater
Indicates that one entity consists of or contains surface-level water associated with another entity.
-
E.
riverMouthElevation
Indicates the elevation at which a river reaches its mouth or endpoint, typically where it flows into another body of water.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5276b0ae48190b2935230363239e0 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:39 p.m.