Triple
T5037702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Chad |
E113465
|
entity |
| Predicate | causeOfShrinkage |
P694
|
FINISHED |
| Object | climate variability |
—
|
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: climate variability | Statement: [Lake Chad, causeOfShrinkage, climate variability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfShrinkage Context triple: [Lake Chad, causeOfShrinkage, climate variability]
-
A.
rinkType
Indicates the specific kind or category of rink associated with an entity (e.g., ice rink, roller rink, practice rink).
-
B.
timePeriodOfMajorShrinkage
Indicates the time period during which a significant reduction or contraction of something occurs.
-
C.
reasonForFurtherDeterioration
Indicates that one condition, event, or factor is identified as the cause of additional worsening or decline in another condition or situation.
-
D.
usesConstriction
Indicates that one entity applies pressure by tightening or squeezing around another entity to restrain, control, or affect it.
-
E.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73daaa788190b670f6c328bfa44f |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.