Triple

T5337339
Position Surface form Disambiguated ID Type / Status
Subject Atlantic Water E123857 entity
Predicate typicallyFoundAtDepth P16570 FINISHED
Object 200–900 m in the Arctic Ocean 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: 200–900 m in the Arctic Ocean | Statement: [Atlantic Water, typicallyFoundAtDepth, 200–900 m in the Arctic Ocean]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicallyFoundAtDepth
Context triple: [Atlantic Water, typicallyFoundAtDepth, 200–900 m in the Arctic Ocean]
  • A. hasAverageDepth
    Indicates that an entity possesses a specified mean depth value, typically measured over its entire extent or area.
  • B. summitDepth
    Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or surrounding terrain.
  • C. depthMetresApprox chosen
    Indicates an approximate measurement of how deep something is in metres, rather than an exact value.
  • D. hasUndergroundDepth
    Indicates that one entity has a specified vertical extent or depth located below the ground surface relative to another reference or context.
  • E. testDepth
    Indicates that an entity is evaluated or measured based on how deep or thorough it is, often in terms of levels, layers, or extent below a surface or baseline.
  • 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.