Triple
T28164291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geiseltal region |
E714981
|
entity |
| Predicate | lakeCreationMethod |
P120406
|
FINISHED |
| Object | flooded open-cast mine |
—
|
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: flooded open-cast mine | Statement: [Geiseltal region, lakeCreationMethod, flooded open-cast mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lakeCreationMethod Context triple: [Geiseltal region, lakeCreationMethod, flooded open-cast mine]
-
A.
lakeCreationPurpose
Indicates the intended purpose or primary function for which a lake was created or established.
-
B.
createsLake
Indicates that one entity causes the formation or existence of a lake in relation to another entity or location.
-
C.
lakeOrigin
chosen
Indicates that a lake originates from, is formed by, or has its source in a specified geographic or hydrological feature.
-
D.
riverFormed
Indicates that a river came into existence or was created, typically as a result of natural geological or hydrological processes.
-
E.
waterBodyCreated
Indicates that one entity is responsible for the formation or creation of a particular 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f641ed2a0c81909246ce42d3e01317 |
completed | May 2, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:08 p.m.