Triple
T346083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tonga Trench |
E6944
|
entity |
| Predicate | waterPressureAtBottom |
P4265
|
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: [Tonga Trench, waterPressureAtBottom, over 1,000 atmospheres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterPressureAtBottom Context triple: [Tonga Trench, waterPressureAtBottom, over 1,000 atmospheres]
-
A.
pressureAtBottom
chosen
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
B.
waterColumnZone
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
-
C.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
D.
waterTemperatureType
Indicates the classification or category of a water body’s temperature (e.g., cold, warm, hot) associated with an entity or context.
-
E.
hasAtmosphericPressureAtSeaLevel
Indicates that an entity possesses a specific value of atmospheric pressure measured at sea level.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb0240e88190bc70784772f5fa30 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.