Triple
T30601094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bitter Lakes |
E778907
|
entity |
| Predicate | salinityComparedTo |
P4654
|
FINISHED |
| Object | higher than average ocean salinity |
—
|
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: higher than average ocean salinity | Statement: [Bitter Lakes, salinityComparedTo, higher than average ocean salinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: salinityComparedTo Context triple: [Bitter Lakes, salinityComparedTo, higher than average ocean salinity]
-
A.
salinity
Indicates the concentration of dissolved salts present in or affecting something, typically a body of water or environment.
-
B.
hasHigherSalinityThan
chosen
Indicates that one entity has a greater concentration of dissolved salts than another entity.
-
C.
salinityPreference
Indicates the preferred range or level of salinity under which an entity most optimally exists, functions, or occurs.
-
D.
salinityRegime
Indicates the pattern or level of salt concentration characterizing an environment or system over time.
-
E.
salinityControlledBy
Indicates that the salinity level of one entity is regulated, influenced, or determined by another entity or process.
- 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689b1d4748190a36530d97480d579 |
completed | May 2, 2026, 11:33 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:25 p.m.