Triple
T34556426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie Ridge seamounts |
E887216
|
entity |
| Predicate | plateMotionDirection |
P2050
|
FINISHED |
| Object | eastward relative to hotspot |
—
|
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: eastward relative to hotspot | Statement: [Carnegie Ridge seamounts, plateMotionDirection, eastward relative to hotspot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plateMotionDirection Context triple: [Carnegie Ridge seamounts, plateMotionDirection, eastward relative to hotspot]
-
A.
plateMotion
chosen
Indicates the movement or displacement of a tectonic plate relative to other plates or a reference frame.
-
B.
subductedDirection
Indicates the direction in which one tectonic plate moves beneath another during subduction.
-
C.
linkedToPlateMotion
Indicates a relationship where a feature, event, or process is causally or functionally connected to the movement of tectonic plates.
-
D.
peakDirectionExpress
Indicates the direction in which a peak (such as a maximum value or intensity) is oriented or expressed.
-
E.
plateConvergenceType
Indicates the specific manner in which tectonic plates move toward and collide with each other at a convergent boundary.
- 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_69f349d0c4d881908dd0950f5eb9ec0a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7205f759c8190b332ae2680adebae |
completed | May 3, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.