Triple
T33644434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serua |
E861919
|
entity |
| Predicate | hasLastKnownEruptionCentury |
P23370
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Serua, hasLastKnownEruptionCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLastKnownEruptionCentury Context triple: [Serua, hasLastKnownEruptionCentury, 20th century]
-
A.
hasLastEruptionCentury
chosen
Indicates the century during which the most recent eruption of a volcano (or eruptive feature) occurred.
-
B.
hasEruptionInCentury
Indicates that an eruption event occurred during a specified century.
-
C.
hasHistoricalEruptionsSince
Indicates that the referenced volcano or geological feature has experienced one or more recorded eruptions since a specified point in time.
-
D.
lastEruption
Indicates the time or event corresponding to the most recent eruption associated with a given entity.
-
E.
hasFrequentEruptionsSince
Indicates that an entity has experienced eruptions repeatedly and at relatively short intervals starting from a specified point in time.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:42 a.m.