Triple
T22069564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yomei Seamount |
E545367
|
entity |
| Predicate | chainTrend |
P146497
|
FINISHED |
| Object | northwest–southeast |
—
|
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: northwest–southeast | Statement: [Yomei Seamount, chainTrend, northwest–southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chainTrend Context triple: [Yomei Seamount, chainTrend, northwest–southeast]
-
A.
chain
Indicates that one entity is linked or connected in sequence to another, typically as part of a series or chain of related elements or actions.
-
B.
chains
Indicates that one entity is physically or metaphorically bound, linked, or restrained by another through chains or a chain-like connection.
-
C.
closureTrend
Indicates how the status or frequency of closures changes over time (e.g., increasing, decreasing, or stable).
-
D.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
E.
chainPosition
Indicates the position or rank an entity occupies within an ordered chain or sequence relative to other entities.
- F. None of above. chosen
Provenance (4 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1288724e881908b38fe7e56d3b448 |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
| PDg | Predicate description generation | batch_69e6fad4a540819096cdd5ea08527220 |
completed | April 21, 2026, 4:19 a.m. |
Created at: April 16, 2026, 8:28 p.m.