Triple
T37175879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Böhlen |
E921039
|
entity |
| Predicate | nearOpenCastMine |
P120102
|
FINISHED |
| Object | Böhlen lignite 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: Böhlen lignite mine | Statement: [Böhlen, nearOpenCastMine, Böhlen lignite mine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearOpenCastMine Context triple: [Böhlen, nearOpenCastMine, Böhlen lignite mine]
-
A.
hasNearbyMine
Indicates that one entity is located close to or in the vicinity of a mine associated with another entity.
-
B.
openedToProspectors
Indicates that access or rights to a resource, area, or opportunity have been made available for exploration, evaluation, or exploitation by prospectors.
-
C.
hasOpenPitMine
Indicates that an entity operates, contains, or is associated with an open-pit mining site.
-
D.
nearestEntrance
Indicates that one entrance is the closest access point to a given location or entity compared to all other possible entrances.
-
E.
hasCoalMineNearby
chosen
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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.