Triple
T22574421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivera microplate |
E544354
|
entity |
| Predicate | separationMechanism |
P81466
|
FINISHED |
| Object | seafloor spreading |
—
|
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: seafloor spreading | Statement: [Rivera microplate, separationMechanism, seafloor spreading]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationMechanism Context triple: [Rivera microplate, separationMechanism, seafloor spreading]
-
A.
separationMethod
Indicates the technique or process used to separate one substance, component, or entity from another.
-
B.
separationProcess
chosen
Indicates a process in which components of a mixture or system are divided or isolated from one another based on differing properties or conditions.
-
C.
typeOfSeparation
Indicates the specific manner or category of separation that exists or occurred between entities.
-
D.
separationPhase
Indicates the phase or stage during which two previously connected entities are being separated or detached from one another.
-
E.
separates
Indicates that one entity divides, parts, or keeps other entities apart from each other.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fec296481908a6101b02e5bedaa |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.