Triple
T978190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Hanshin earthquake |
E21104
|
entity |
| Predicate | faultType |
P3827
|
FINISHED |
| Object | strike-slip fault |
—
|
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: strike-slip fault | Statement: [Great Hanshin earthquake, faultType, strike-slip fault]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faultType Context triple: [Great Hanshin earthquake, faultType, strike-slip fault]
-
A.
typeOfFaulting
chosen
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
B.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or situation.
-
C.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
D.
resolutionType
Indicates the specific manner or category by which an issue, event, or conflict is resolved or brought to a conclusion.
-
E.
fuseType
Indicates the specific kind or category of fuse associated with or used in relation to an entity.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b47861808190be56a7bbd926e658 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a8a3b08190b4538e119b13f7f5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.