Triple
T28323280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saxony-Leipzig lignite mining area |
E717334
|
entity |
| Predicate | landUseAfterMining |
P164271
|
FINISHED |
| Object | lakes |
—
|
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: lakes | Statement: [Saxony-Leipzig lignite mining area, landUseAfterMining, lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landUseAfterMining Context triple: [Saxony-Leipzig lignite mining area, landUseAfterMining, lakes]
-
A.
landUseChangeTo
Indicates a transition in how a piece of land is used, from its previous use to a new designated use.
-
B.
formerLandUse
Indicates the type of land use that characterized a location prior to its current or present use.
-
C.
otherLandUse
Indicates that the land is used for purposes that do not fall into any of the primary or predefined land-use categories.
-
D.
majorLandUse
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
E.
siteUseAfterDemolition
Indicates the subsequent use or function assigned to a site following the demolition of its previous structures.
- F. None of above. chosen
Provenance (4 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_69eff6e6c3b08190ad78de6ba7f04548 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f6492ce1ec81908f51388ed8eea019 |
completed | May 2, 2026, 6:57 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 28, 2026, 12:26 a.m.