Triple
T15633558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nankai segment |
E375879
|
entity |
| Predicate | ruptureStyle |
P12065
|
FINISHED |
| Object | megathrust faulting |
—
|
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 faulting | Statement: [Nankai segment, ruptureStyle, megathrust faulting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruptureStyle Context triple: [Nankai segment, ruptureStyle, megathrust faulting]
-
A.
breaksWith
Indicates that one entity ends or disrupts an existing association, agreement, or alignment with another entity.
-
B.
breakType
Indicates the specific kind or category of break or interruption that occurs in a process, activity, or sequence.
-
C.
spontaneouslyBrokenBy
Indicates that a symmetry or property is not explicitly violated by the underlying laws but is instead broken by the system’s ground state or configuration due to spontaneous symmetry breaking caused by the specified entity or mechanism.
-
D.
structuralStyle
Indicates the architectural or design style that characterizes the structure or form of an entity.
-
E.
deformationStyle
chosen
Indicates the manner or pattern in which an object or material is deformed under applied forces or conditions.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eb7338881909f3c430bb73f91d1 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.