Triple
T34501719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carnegie Ridge |
E885773
|
entity |
| Predicate | maximumReliefAboveAbyssalPlain |
P15453
|
FINISHED |
| Object | more than 2 km |
—
|
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: more than 2 km | Statement: [Carnegie Ridge, maximumReliefAboveAbyssalPlain, more than 2 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumReliefAboveAbyssalPlain Context triple: [Carnegie Ridge, maximumReliefAboveAbyssalPlain, more than 2 km]
-
A.
maximumHeightAboveSeafloor
chosen
Indicates the greatest vertical distance between an object or feature and the seafloor beneath it.
-
B.
seafloorDepthRelativeToAbyssalPlains
Indicates how the depth of a given seafloor location compares to the typical depth of abyssal plains, such as being deeper, shallower, or at a similar depth.
-
C.
maximumDepthBelowSeaLevel
Indicates the greatest vertical distance an entity extends or reaches below sea level.
-
D.
maximumDepthKilometres
Indicates the greatest depth, measured in kilometers, that something reaches or extends to.
-
E.
maximumVolcanicRelief
Indicates the greatest vertical difference in elevation within a volcanic landform or volcanic region.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 2:01 a.m.