Triple
T18054649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ptolemaida lignite basin |
E432004
|
entity |
| Predicate | transitionIssue |
P129647
|
FINISHED |
| Object | just transition for coal regions |
—
|
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: just transition for coal regions | Statement: [Ptolemaida lignite basin, transitionIssue, just transition for coal regions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionIssue Context triple: [Ptolemaida lignite basin, transitionIssue, just transition for coal regions]
-
A.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
B.
transitionReason
Indicates the cause, motivation, or triggering factor behind a change from one state, status, or condition to another.
-
C.
transitionState
Indicates a change in condition or phase from one defined state to another within a process or system.
-
D.
transitionTo
Indicates a change in state, condition, or phase from one defined status to another.
-
E.
transitionProgram
Indicates a relationship where one entity serves as a program or structured process that facilitates another entity’s transition from one state, phase, or condition to another.
- 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_69d8b906482481908183315b9ecf9994 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4c101dfb081908dc66f4b4967d8c7 |
completed | April 19, 2026, 11:48 a.m. |
| PD | Predicate disambiguation | batch_69e3f90c652481908133a73106d78919 |
completed | April 18, 2026, 9:35 p.m. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:26 a.m.