Triple
T28952553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geiseltalsee |
E731056
|
entity |
| Predicate | locatedInMiningArea |
P80678
|
FINISHED |
| Object | Geiseltal lignite mining district |
—
|
NE NERFINISHED |
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: Geiseltal lignite mining district | Statement: [Geiseltalsee, locatedInMiningArea, Geiseltal lignite mining district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMiningArea Context triple: [Geiseltalsee, locatedInMiningArea, Geiseltal lignite mining district]
-
A.
locatedInMiningDistrict
Indicates that one entity is situated within the geographic or administrative boundaries of a specified mining district.
-
B.
locatedInMiningBelt
Indicates that an entity is situated within a designated mining belt or mining region.
-
C.
locatedInFormerMiningArea
chosen
Indicates that an entity is situated within an area that was previously used for mining activities.
-
D.
locatedInMineType
Indicates that something is situated within or associated with a specific type of mine.
-
E.
hasCoalMineNearby
Indicates that a location or entity is situated close to at least one coal mine.
- 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_69f043eb9bcc819091ac7b07aecb6475 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ffdf47d9608190830ca23d9cef6409 |
completed | May 10, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ffdf00e2b4819082dd5cb78f316baf |
completed | May 10, 2026, 1:27 a.m. |
Created at: April 28, 2026, 8:44 a.m.