Triple
T33037480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edersee Dam |
E845356
|
entity |
| Predicate | hasMaximumDepthInReservoir |
P42760
|
FINISHED |
| Object | 41 m |
—
|
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: 41 m | Statement: [Edersee Dam, hasMaximumDepthInReservoir, 41 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumDepthInReservoir Context triple: [Edersee Dam, hasMaximumDepthInReservoir, 41 m]
-
A.
hasApproximateLakeDepth
Indicates that an entity is associated with a lake whose depth is given as an estimated or non-exact value.
-
B.
maximumWaterDepth
chosen
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
C.
hasCaissonWaterDepth
Indicates the depth of water surrounding or contained within a caisson in a given context.
-
D.
hasWaterDepthAtExit
Indicates the water depth measured at the exit point of a structure, channel, or system.
-
E.
reservoirLength
Indicates the measured longitudinal extent of a reservoir from one end to the other.
- 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_69f34951348c8190b56746b0a7018182 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a00bb3a6f888190b3ecd0fbc9af9b4a |
completed | May 10, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_6a00b902dbf881909e098ff102b7ea7e |
completed | May 10, 2026, 4:57 p.m. |
Created at: May 1, 2026, 1:24 a.m.