Triple
T24710221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpine Fault |
E612005
|
entity |
| Predicate | lastMajorRupture |
P110818
|
FINISHED |
| Object | around 1717 CE |
—
|
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: around 1717 CE | Statement: [Alpine Fault, lastMajorRupture, around 1717 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lastMajorRupture Context triple: [Alpine Fault, lastMajorRupture, around 1717 CE]
-
A.
hasLastMajorSurfaceRuptureIn
chosen
Indicates that an entity experienced its most recent significant surface-rupturing event within a specified time or temporal interval.
-
B.
lastMajorEruptivePeriod
Indicates the most recent significant time span during which a volcano or eruptive system experienced major eruptive activity.
-
C.
lastMajorCollapse
Indicates the most recent significant breakdown or failure event that occurred in relation to the subject.
-
D.
lastMajorEruptionIncludes
Indicates that the specified event or time period is part of, or falls within, the volcano’s most recent major eruption.
-
E.
lastMajorEvent
Indicates the most recent significant event associated with an entity in a given context.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:24 a.m.