Triple
T6020362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samalas volcano |
E134046
|
entity |
| Predicate | eruptionDateApproximation |
P20891
|
FINISHED |
| Object | between May and October 1257 |
—
|
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: between May and October 1257 | Statement: [Samalas volcano, eruptionDateApproximation, between May and October 1257]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eruptionDateApproximation Context triple: [Samalas volcano, eruptionDateApproximation, between May and October 1257]
-
A.
lastEruptionApproximateDate
Indicates that the recorded date of the most recent eruption is an estimate rather than an exact, precisely known date.
-
B.
eruptionPeakDate
Indicates the specific date on which an eruption reaches its maximum intensity or peak activity.
-
C.
notableEruptionAge
Indicates the age or time period at which a notable volcanic eruption associated with an entity occurred.
-
D.
eruptionStartDate
Indicates the date on which an eruption event begins.
-
E.
majorEruptionYear
chosen
Indicates the calendar year in which a volcano or similar geological feature experienced a major eruption.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f86efec8190bc357dddf6ebb4a9 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:07 p.m.