Triple
T34607580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hōei era |
E888636
|
entity |
| Predicate | HōeiEarthquakeType |
P28044
|
FINISHED |
| Object | megathrust earthquake |
—
|
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: megathrust earthquake | Statement: [Hōei era, HōeiEarthquakeType, megathrust earthquake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HōeiEarthquakeType Context triple: [Hōei era, HōeiEarthquakeType, megathrust earthquake]
-
A.
earthquakeType
chosen
Indicates the specific classification or category of an earthquake based on its characteristics or cause.
-
B.
temporalRelationToHōeiEarthquake
Indicates the temporal relationship an event or state has to the Hōei Earthquake, such as occurring before, during, or after that specific historical earthquake.
-
C.
notableEarthquake
Indicates that an earthquake event is significant or noteworthy due to its magnitude, impact, or historical importance.
-
D.
tsunamiType
Indicates the specific classification or category of a tsunami associated with an event or location.
-
E.
strongestShakingArea
Indicates the area that experiences the most intense level of shaking relative to surrounding regions.
- 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_69f349d489d48190ba30e7d97c6f5ef9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f728a345488190bd7e6751b09ac591 |
completed | May 3, 2026, 10:51 a.m. |
| PD | Predicate disambiguation | batch_69f7283ef2608190a7a85d7e7f5332c0 |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 2:03 a.m.