Triple
T111043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juan de Fuca Plate |
E2247
|
entity |
| Predicate | causes |
P694
|
FINISHED |
| Object | interplate 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: interplate earthquakes | Statement: [Juan de Fuca Plate, causes, interplate earthquakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causes Context triple: [Juan de Fuca Plate, causes, interplate earthquakes]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeOfDeath
Indicates the specific factor, event, or condition that directly resulted in an entity’s death.
-
C.
issues
Indicates that an entity formally produces, releases, or distributes something, such as a document, order, or resource, making it officially available.
-
D.
hasCause
Indicates that one entity is the reason for, or brings about, the occurrence or existence of another entity or event.
-
E.
underlies
Indicates that one entity serves as a fundamental basis, support, or underlying cause for another entity, condition, or phenomenon.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a258b58efc8190959c86f73d67b744 |
completed | Feb. 28, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69a25641058c8190b5b64509b35d8176 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.