Triple
T216828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molloy Deep |
E4122
|
entity |
| Predicate | waterMassInfluence |
P8157
|
FINISHED |
| Object | Arctic deep water |
—
|
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: Arctic deep water | Statement: [Molloy Deep, waterMassInfluence, Arctic deep water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterMassInfluence Context triple: [Molloy Deep, waterMassInfluence, Arctic deep water]
-
A.
waterMassType
Indicates the classification of a body of water according to its physical or compositional type.
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
-
D.
locatedInBodyOfWater
Indicates that an entity is situated within or on the surface of a specific body of water.
-
E.
marineArea
Indicates a relationship where an entity is located in, associated with, or relevant to a specific marine or oceanic area.
- F. None of above. chosen
Provenance (4 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_69a2573508588190b522c2476d91acfe |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25c4edfa081909fe97c86c3c7801d |
completed | Feb. 28, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69a25b5357bc8190b29a48e3053fb76d |
completed | Feb. 28, 2026, 3:04 a.m. |
| PDg | Predicate description generation | batch_69a25be349588190aedde33d80682344 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:53 a.m.