Triple
T1079305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vredefort Dome |
E23910
|
entity |
| Predicate | impactEffects |
P5628
|
FINISHED |
| Object | regional crustal deformation |
—
|
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: regional crustal deformation | Statement: [Vredefort Dome, impactEffects, regional crustal deformation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactEffects Context triple: [Vredefort Dome, impactEffects, regional crustal deformation]
-
A.
socialImpact
Indicates the extent to which an action, entity, or relationship affects society or communities, whether positively or negatively.
-
B.
humanImpact
Indicates the effect or influence that human activities have on another entity, system, or environment.
-
C.
hasEnvironmentalImpactOn
chosen
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
-
D.
impactOnPerformance
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
-
E.
climateChangeEffect
Indicates how climate change influences or alters a particular entity, condition, or process.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.