Triple
T22781904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nintoku Seamount |
E563861
|
entity |
| Predicate | underseaFeature |
P137559
|
FINISHED |
| Object | submerged volcanic edifice |
—
|
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: submerged volcanic edifice | Statement: [Nintoku Seamount, underseaFeature, submerged volcanic edifice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underseaFeature Context triple: [Nintoku Seamount, underseaFeature, submerged volcanic edifice]
-
A.
partOfUnderseaFeature
Indicates that one undersea feature is a component or subdivision of a larger undersea feature.
-
B.
seaBedFeature
chosen
Indicates that an entity is a physical feature or formation located on or forming part of the seabed.
-
C.
seafloorType
Indicates the classification of the ocean bottom surface based on its physical or geological characteristics.
-
D.
oceanographicFeature
Indicates that one entity is an oceanographic feature (such as a current, front, eddy, or water mass) associated with or characterizing another entity.
-
E.
oceanPresence
Indicates that an entity is located in, adjacent to, or significantly influenced by an ocean.
- 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_69e2455500788190b4b33030461f3bbd |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17c2dd250819093a5c49806916ec4 |
completed | April 29, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.