Triple
T2390292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Australian Current |
E48924
|
entity |
| Predicate | waterMassOrigin |
P12617
|
FINISHED |
| Object | subantarctic waters |
—
|
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: subantarctic waters | Statement: [West Australian Current, waterMassOrigin, subantarctic waters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterMassOrigin Context triple: [West Australian Current, waterMassOrigin, subantarctic waters]
-
A.
waterMassType
Indicates the classification of a body of water according to its physical or compositional type.
-
B.
waterMassInfluence
Indicates how the presence, amount, or distribution of water mass affects or modifies another entity or system.
-
C.
waterOrigin
chosen
Indicates the source or starting location from which the water originates or is supplied.
-
D.
waterMassProperty
Indicates a relationship where a specific physical or chemical property is attributed to a body or mass of water.
-
E.
includesWaterMass
Indicates that one entity contains, encompasses, or has within its boundaries a 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc7de1478819082238e8b8f88ed06 |
completed | March 7, 2026, 6:38 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.