Triple
T1038153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Bromo |
E22411
|
entity |
| Predicate | previousNotableEruption |
P24233
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [Mount Bromo, previousNotableEruption, 2010]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousNotableEruption Context triple: [Mount Bromo, previousNotableEruption, 2010]
-
A.
notableEruption
Indicates that a volcano or geothermal feature has experienced an eruption considered historically or scientifically significant.
-
B.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
C.
lastEruptionStartDate
Indicates the date on which the most recent eruption of the entity began.
-
D.
firstRecordedEruption
Indicates the time or event of the earliest known or documented eruption associated with a volcano or eruptive feature.
-
E.
majorEruptionYear
Indicates the calendar year in which a volcano or similar geological feature experienced a major eruption.
- F. None of above. chosen
Provenance (4 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b97c64a88190bf1119fdd4940bf3 |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b729f8488190b2042bd9c625a833 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b97acbf4819087b92a8b29baef46 |
completed | March 1, 2026, 10:11 p.m. |
Created at: March 1, 2026, 7:41 p.m.