Triple
T8358513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Labrador Sea Water |
E196739
|
entity |
| Predicate | waterMassCoreProperty |
P24729
|
FINISHED |
| Object | low potential vorticity core |
—
|
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: low potential vorticity core | Statement: [Labrador Sea Water, waterMassCoreProperty, low potential vorticity core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterMassCoreProperty Context triple: [Labrador Sea Water, waterMassCoreProperty, low potential vorticity core]
-
A.
waterMassProperty
chosen
Indicates a relationship where a specific physical or chemical property is attributed to a body or mass of water.
-
B.
waterMassType
Indicates the classification of a body of water according to its physical or compositional type.
-
C.
includesWaterMass
Indicates that one entity contains, encompasses, or has within its boundaries a body or mass of water.
-
D.
waterMassInfluence
Indicates how the presence, amount, or distribution of water mass affects or modifies another entity or system.
-
E.
hasWaterMassOrigin
Indicates that something originates from, or is derived from, a particular body or mass of water.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb806fa5c88190b23b6b3ee9d6ec6d |
completed | March 31, 2026, 8:06 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:59 p.m.