Triple
T32358482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paralichthys |
E826795
|
entity |
| Predicate | benthicZone |
P90934
|
FINISHED |
| Object | continental shelf |
—
|
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: continental shelf | Statement: [Paralichthys, benthicZone, continental shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benthicZone Context triple: [Paralichthys, benthicZone, continental shelf]
-
A.
benthicAssociation
chosen
Indicates a relationship in which one entity is associated with, lives on, or interacts closely with the bottom (benthic) zone of a body of water.
-
B.
sideRestingOnSeafloor
Indicates that one side of an object is in direct contact with and supported by the seafloor.
-
C.
marineBiodiversityLevel
Indicates the degree or richness of species variety and ecological complexity present within a marine environment.
-
D.
isSubseaBasinOf
Indicates that a geological basin is located beneath the sea and is part of, or contained within, a larger marine or oceanic region.
-
E.
partOfUnderseaFeature
Indicates that one undersea feature is a component or subdivision of a larger undersea feature.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:49 a.m.