Triple
T648427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brownson Deep |
E11291
|
entity |
| Predicate | waterColumn |
P7312
|
FINISHED |
| Object | very high hydrostatic pressure |
—
|
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: very high hydrostatic pressure | Statement: [Brownson Deep, waterColumn, very high hydrostatic pressure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterColumn Context triple: [Brownson Deep, waterColumn, very high hydrostatic pressure]
-
A.
waterColumnZone
chosen
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
-
B.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
C.
waterFlowRate
Indicates the rate at which water moves or is transported through a given point or system over time.
-
D.
pressureAtBottom
Indicates that a specified amount of pressure is exerted or present at the bottom of a given object, container, or region.
-
E.
waterColor
Indicates that one entity is the color or hue characteristic of water associated with another entity.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f308f34819094ba28cfc786051e |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.