Triple
T20064603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hohenwarte Dam |
E499574
|
entity |
| Predicate | isMajorReservoir |
P11014
|
FINISHED |
| Object | one of the largest reservoirs in Germany |
—
|
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: one of the largest reservoirs in Germany | Statement: [Hohenwarte Dam, isMajorReservoir, one of the largest reservoirs in Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorReservoir Context triple: [Hohenwarte Dam, isMajorReservoir, one of the largest reservoirs in Germany]
-
A.
hasMajorReservoir
Indicates that an entity possesses or is associated with a primary or significant reservoir (such as a large storage or accumulation of a resource).
-
B.
majorReservoir
chosen
Indicates that one entity functions as a primary or significant water-storage reservoir associated with another entity.
-
C.
isReservoir
Indicates that one entity functions as a storage or holding container (often for fluids or resources) for another entity.
-
D.
isLargestReservoirIn
Indicates that one entity is the largest reservoir located within or associated with another entity (such as a region, river system, or administrative area).
-
E.
hasUpperReservoir
Indicates that one entity possesses or is associated with an upper-level reservoir in relation to another component or system.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663787190819096b2b78b38c1bf12 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.