Triple
T5337351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Water |
E123857
|
entity |
| Predicate | hasTypicalSalinityRange |
P1181
|
FINISHED |
| Object | 34.8–35.2 practical salinity units |
—
|
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: 34.8–35.2 practical salinity units | Statement: [Atlantic Water, hasTypicalSalinityRange, 34.8–35.2 practical salinity units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalSalinityRange Context triple: [Atlantic Water, hasTypicalSalinityRange, 34.8–35.2 practical salinity units]
-
A.
hasSalinityRange
chosen
Indicates the range of salinity values within which something (such as a substance, environment, or organism) is present, applicable, or able to function.
-
B.
salinityPreference
Indicates the preferred range or level of salinity under which an entity most optimally exists, functions, or occurs.
-
C.
hasSalinityIssue
Indicates that an entity is affected by or associated with a problem related to salinity levels.
-
D.
salinityRegime
Indicates the pattern or level of salt concentration characterizing an environment or system over time.
-
E.
hasHigherSalinityThan
Indicates that one entity has a greater concentration of dissolved salts than 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85c6ec008190ad7a8a54360387d8 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd84583dbc819088a03e3afb30178c |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2 p.m.