Triple
T38195305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Eifel volcanic field |
E1005592
|
entity |
| Predicate | LaacherSeeEruptionAge |
P34963
|
FINISHED |
| Object | Late Pleistocene |
—
|
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: Late Pleistocene | Statement: [East Eifel volcanic field, LaacherSeeEruptionAge, Late Pleistocene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LaacherSeeEruptionAge Context triple: [East Eifel volcanic field, LaacherSeeEruptionAge, Late Pleistocene]
-
A.
notableEruptionAge
chosen
Indicates the age or time period at which a notable volcanic eruption associated with an entity occurred.
-
B.
lastEruptionApproximateDate
Indicates that the recorded date of the most recent eruption is an estimate rather than an exact, precisely known date.
-
C.
volcanicFieldAge
Indicates the age or geological time period during which a volcanic field formed or was active.
-
D.
lastEruptionEndYear
Indicates the calendar year in which the most recent volcanic eruption concluded.
-
E.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given 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_69f76dbd22f48190940318cea061e8bb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:29 p.m.