Triple
T15376172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Ocean seafloor |
E367673
|
entity |
| Predicate | sedimentSources |
P2051
|
FINISHED |
| Object | riverine input |
—
|
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: riverine input | Statement: [Arctic Ocean seafloor, sedimentSources, riverine input]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sedimentSources Context triple: [Arctic Ocean seafloor, sedimentSources, riverine input]
-
A.
sedimentSource
chosen
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
B.
causeOfSediment
Indicates that one entity is the source or generating factor responsible for the formation or presence of sediment in another entity or location.
-
C.
roleInSedimentDynamics
Indicates the function or influence an entity has in controlling, modifying, or participating in sediment transport, deposition, or erosion processes.
-
D.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
E.
hasSedimentLoad
Indicates that one entity (typically a water body or flow) carries or transports a certain amount or type of sediment associated with another entity.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:18 a.m.