Triple
T32545764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1964 Alaska earthquake |
E831843
|
entity |
| Predicate | occurredOnFault |
P60124
|
FINISHED |
| Object | Aleutian Megathrust |
—
|
NE NERFINISHED |
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: Aleutian Megathrust | Statement: [1964 Alaska earthquake, occurredOnFault, Aleutian Megathrust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurredOnFault Context triple: [1964 Alaska earthquake, occurredOnFault, Aleutian Megathrust]
-
A.
associatedFault
chosen
Indicates a relationship where a given entity is linked to, or occurs in connection with, a specific fault or error condition.
-
B.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
-
C.
accidentOccurredDuring
Indicates that an accident took place within the time span or context of a specified event, activity, or condition.
-
D.
injuryOccurredAt
Indicates that an injury took place at a specific location or during a particular event or time.
-
E.
typeOfFaulting
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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c5bfe55881909a20ef79180d19c4 |
completed | May 3, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.