Triple
T15376176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arctic Ocean seafloor |
E367673
|
entity |
| Predicate | sedimentComposition |
P18668
|
FINISHED |
| Object | clays |
—
|
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: clays | Statement: [Arctic Ocean seafloor, sedimentComposition, clays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sedimentComposition Context triple: [Arctic Ocean seafloor, sedimentComposition, clays]
-
A.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
B.
typicalSedimentSizeRange
Indicates the usual range of sediment particle sizes associated with an entity or environment.
-
C.
hasSedimentsThat
chosen
Indicates that one entity contains, includes, or is associated with specific sediments described by the related entity.
-
D.
sedimentSource
Indicates that one entity serves as the origin or provider of sediment that is transported to or deposited in another entity.
-
E.
sedimentaryStructure
Indicates a relationship where a geological entity exhibits or is characterized by a particular sedimentary structure formed during deposition or shortly thereafter.
- 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.