Triple
T23364274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vredefort Dome |
E593268
|
entity |
| Predicate | impactEventType |
P51728
|
FINISHED |
| Object | meteorite impact |
—
|
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: meteorite impact | Statement: [Vredefort Dome, impactEventType, meteorite impact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactEventType Context triple: [Vredefort Dome, impactEventType, meteorite impact]
-
A.
impactEvent
Indicates that one entity physically strikes or collides with another, producing a resulting effect or change.
-
B.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
-
C.
impactCategory
chosen
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
D.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
E.
impactOutcome
Indicates that one entity produces an effect or influence that changes the result, consequence, or final state of another entity or situation.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aac4248190a4663ed12aed6856 |
completed | April 29, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:31 p.m.