Triple
T15235188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greensand |
E364109
|
entity |
| Predicate | hasTypicalEnvironmentOfDeposition |
P88863
|
FINISHED |
| Object | shallow marine 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: shallow marine shelf | Statement: [Greensand, hasTypicalEnvironmentOfDeposition, shallow marine shelf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalEnvironmentOfDeposition Context triple: [Greensand, hasTypicalEnvironmentOfDeposition, shallow marine shelf]
-
A.
depositionalEnvironment
Indicates the natural setting or conditions under which sediments were originally deposited.
-
B.
typicalGeologicEnvironment
chosen
Indicates the characteristic geologic setting or conditions in which something (such as a rock, mineral, or process) most commonly occurs or forms.
-
C.
fossilEnvironment
Indicates the type of environment or setting in which a fossil was originally formed or deposited.
-
D.
hasSedimentaryBasin
Indicates that a geological region or area contains or is associated with a sedimentary basin.
-
E.
hasSedimentsThat
Indicates that one entity contains, includes, or is associated with specific sediments described by the related 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d91e4881908ea52d11a3d4480a |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.