Triple
T22544925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Düzce earthquake |
E557393
|
entity |
| Predicate | typeOfRupture |
P3827
|
FINISHED |
| Object | right-lateral strike-slip |
—
|
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: right-lateral strike-slip | Statement: [1999 Düzce earthquake, typeOfRupture, right-lateral strike-slip]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRupture Context triple: [1999 Düzce earthquake, typeOfRupture, right-lateral strike-slip]
-
A.
ruptureDate
Indicates the date on which a rupture event (such as a break, burst, or failure) occurs in the relationship between entities.
-
B.
rupturesDuring
Indicates that one event or process ruptures or breaks while another specified event or time period is occurring.
-
C.
typeOfDam
Indicates the specific kind or classification of a dam associated with an entity.
-
D.
rupturedSegmentOf
Indicates that one entity is a segment that has undergone rupture and is part of, or derived from, another entity.
-
E.
typeOfFaulting
chosen
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f34a0688190ad55be067db8e21b |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:51 p.m.