Triple
T1079285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vredefort Dome |
E23910
|
entity |
| Predicate | impactEnergy |
P5332
|
FINISHED |
| Object | extremely high-energy event |
—
|
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: extremely high-energy event | Statement: [Vredefort Dome, impactEnergy, extremely high-energy event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactEnergy Context triple: [Vredefort Dome, impactEnergy, extremely high-energy event]
-
A.
impactOnPerformance
Indicates that one entity has an effect, influence, or consequence on the performance level or effectiveness of another entity.
-
B.
inPower
Indicates that one entity currently holds governing authority, control, or leadership over a group, organization, or domain.
-
C.
energyType
chosen
Indicates the kind or category of energy associated with an entity or process.
-
D.
designEnergy
Indicates that an entity is responsible for planning, specifying, or determining the energy-related characteristics or performance of another entity.
-
E.
hasEnvironmentalImpactOn
Indicates that one entity affects or alters the environmental conditions, quality, or ecological state of another entity.
- 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.