Triple
T35397217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenian coal mining region |
E1023113
|
entity |
| Predicate | transitionTopic |
P199669
|
FINISHED |
| Object | just transition |
—
|
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 | Statement: [Slovenian coal mining region, transitionTopic, just transition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionTopic Context triple: [Slovenian coal mining region, transitionTopic, just transition]
-
A.
transition
Indicates a change of state or condition from one form, phase, or situation to another.
-
B.
transitionNote
Indicates a note or annotation that describes or qualifies a change, shift, or transition from one state, condition, or context to another.
-
C.
transitionIssue
Indicates a problem or complication that arises during the process of moving from one state, phase, or condition to another.
-
D.
transitionFocus
Indicates a change of attention or emphasis from one entity, state, or topic to another.
-
E.
transitionUse
Indicates a relationship where one state, condition, or resource is used as part of moving or changing into another state, condition, or resource.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
| PDg | Predicate description generation | batch_69ff4de56fd48190aefdbf13c70f76ce |
completed | May 9, 2026, 3:08 p.m. |
Created at: May 3, 2026, 4:03 p.m.