Triple
T27846220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turów lignite mine |
E703827
|
entity |
| Predicate | plannedClosureDiscussedIn |
P170386
|
FINISHED |
| Object | 2030s |
—
|
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: 2030s | Statement: [Turów lignite mine, plannedClosureDiscussedIn, 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedClosureDiscussedIn Context triple: [Turów lignite mine, plannedClosureDiscussedIn, 2030s]
-
A.
discussedAs
Indicates that one entity is talked about, treated, or examined in terms of another entity, often as an example, case, or framing concept.
-
B.
closureReason
Indicates the reason or cause for which an entity, process, or case has been closed or terminated.
-
C.
discussed
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
D.
closingTopic
Indicates that one entity brings a discussion, issue, or conversational thread to an end or final resolution.
-
E.
closureAnnouncedBy
Indicates that an entity’s closure has been formally communicated or declared by a specified agent or source.
- 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_69ef840d9e3c819093615ebff4ec22be |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69063edbc81909e7735954aabee0b |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68f6584a88190a8c4d95c0c84bee9 |
completed | May 2, 2026, 11:57 p.m. |
Created at: April 27, 2026, 6:07 p.m.