Triple
T10454100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mariana Trench region |
E246505
|
entity |
| Predicate | maximumPressure |
P56372
|
FINISHED |
| Object | over 1,000 atmospheres |
—
|
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: over 1,000 atmospheres | Statement: [Mariana Trench region, maximumPressure, over 1,000 atmospheres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumPressure Context triple: [Mariana Trench region, maximumPressure, over 1,000 atmospheres]
-
A.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
B.
minimumCentralPressure_mbar
Indicates the lowest atmospheric pressure at the center of a system or event, measured in millibars.
-
C.
minimumCentralPressure_hPa
Indicates the lowest atmospheric pressure at the center of a system, measured in hectopascals (hPa), typically used for phenomena like storms or cyclones.
-
D.
pressureCapability
chosen
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
E.
maximumDischarge
Indicates the greatest allowable or observed rate at which something can be discharged or released from a source.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe47fee48190b38ec0466ff0165a |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:17 p.m.