Triple
T31761747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brochis |
E810697
|
entity |
| Predicate | waterLayer |
P180948
|
FINISHED |
| Object | demersal |
—
|
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: demersal | Statement: [Brochis, waterLayer, demersal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterLayer Context triple: [Brochis, waterLayer, demersal]
-
A.
waterMassLayer
chosen
Indicates a relationship where one water mass is organized as a distinct layer within a stratified body of water, typically differentiated by properties such as temperature, salinity, or density.
-
B.
waterBodyView
Indicates that an entity has a visual outlook or view onto a body of water, such as a lake, river, or ocean.
-
C.
waterFeature
Indicates the presence of a natural or artificial body or flow of water associated with the subject.
-
D.
waterBodyCreated
Indicates that one entity is responsible for the formation or creation of a particular body of water.
-
E.
waterFilled
Indicates that one entity is filled or occupied with water, typically to a certain level or capacity.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: April 30, 2026, 11:31 p.m.