Triple
T25162769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ansei |
E626484
|
entity |
| Predicate | hasTypeOfDisaster |
P155803
|
FINISHED |
| Object | earthquakes |
—
|
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: earthquakes | Statement: [Ansei, hasTypeOfDisaster, earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfDisaster Context triple: [Ansei, hasTypeOfDisaster, earthquakes]
-
A.
hasDisaster
Indicates that an entity experiences, is affected by, or is associated with a disaster event.
-
B.
typeOfDisaster
chosen
Indicates that one entity is classified as a specific kind or category of disaster in relation to another entity.
-
C.
supportsDisasterType
Indicates that one entity is capable of handling, responding to, or being applicable to a specified type of disaster.
-
D.
hasDisasterElement
Indicates that something includes, involves, or is characterized by an element or aspect of a disaster.
-
E.
notableDisasterType
Indicates the specific kind or category of disaster for which something (such as a place, event, or entity) is notable or best known.
- 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_69e2ff2834ec8190b0872e2ec3d76023 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 18, 2026, 6:31 a.m.