Triple
T5605068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalonia |
E147213
|
entity |
| Predicate | riftEventType |
P7008
|
FINISHED |
| Object | continental rifting |
—
|
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: continental rifting | Statement: [Avalonia, riftEventType, continental rifting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riftEventType Context triple: [Avalonia, riftEventType, continental rifting]
-
A.
riftSystem
Indicates a geological relationship where a region is part of, or associated with, a rift system formed by extensional tectonic processes.
-
B.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
C.
formationEvent
Indicates the event or process through which something comes into existence, is created, or is initially established.
-
D.
trapType
Indicates the specific kind or category of trap associated with an entity or situation.
-
E.
typicalEvent
chosen
Indicates that the associated event is a common, characteristic, or prototypical occurrence for the given entity or situation.
- 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_69c0090500f881908374285baf0ac46f |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020fa4b0881909fdbb8ea38eeb5e3 |
completed | March 22, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69c01b1890ec8190b9e6fa488792e4d4 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:39 p.m.