Triple
T28711592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antarctic ozone hole |
E729843
|
entity |
| Predicate | expectedRecovery |
P53924
|
FINISHED |
| Object | mid-21st century or later |
—
|
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: mid-21st century or later | Statement: [Antarctic ozone hole, expectedRecovery, mid-21st century or later]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedRecovery Context triple: [Antarctic ozone hole, expectedRecovery, mid-21st century or later]
-
A.
errorRecovery
Indicates that an entity detects a failure or error condition and initiates actions to restore normal or acceptable operation.
-
B.
designedToRecover
Indicates that something is intentionally created or configured for the purpose of regaining a prior state, condition, or resource after loss, damage, or failure.
-
C.
recovery
chosen
Indicates the process or state in which an entity regains a previous condition, function, or status after loss, damage, or decline.
-
D.
expectedAction
Indicates that a particular action is anticipated or required to occur in a given context or scenario.
-
E.
wasUnexpected
Indicates that an event, outcome, or situation occurred without prior anticipation or contrary to what was expected.
- 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656d86d208190a537ece58e319ed4 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:48 a.m.