Triple
T997340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farallon Plate |
E21523
|
entity |
| Predicate | beganSubduction |
P19545
|
FINISHED |
| Object | Mesozoic era |
—
|
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: Mesozoic era | Statement: [Farallon Plate, beganSubduction, Mesozoic era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganSubduction Context triple: [Farallon Plate, beganSubduction, Mesozoic era]
-
A.
subductsBeneath
Indicates that one entity moves downward and underneath another, typically as part of a convergent or overriding interaction.
-
B.
subductionStyle
Indicates the manner or mode in which one tectonic plate descends beneath another at a convergent plate boundary.
-
C.
subductionZoneName
Indicates the specific name assigned to a subduction zone where one tectonic plate is forced beneath another.
-
D.
began
chosen
Indicates that one entity initiated or started an action, event, or state involving another entity or context.
-
E.
hasPlateTectonics
Indicates that a planetary body exhibits active plate tectonics, with its outer shell divided into moving plates that interact over geological time.
- 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e0f0d081908b888c246d001786 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2af071c819086c374a16307dfe0 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.