Triple
T36925701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain Formation |
E913336
|
entity |
| Predicate | typeOfSedimentaryRock |
P17895
|
FINISHED |
| Object | clastic |
—
|
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: clastic | Statement: [Fountain Formation, typeOfSedimentaryRock, clastic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSedimentaryRock Context triple: [Fountain Formation, typeOfSedimentaryRock, clastic]
-
A.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
B.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
C.
lithostratigraphicType
Indicates the specific lithostratigraphic classification or unit type that characterizes a rock body or stratigraphic unit within a geological framework.
-
D.
lithology
chosen
Indicates the type and characteristics of rock or sediment that compose a geological unit or layer.
-
E.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
- 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_69f76e896c988190880c130e01303dd4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0337c7389c8190b71d27b8eb8daf9a |
completed | May 12, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_6a0335b7b1588190b02a0ce6a08704aa |
completed | May 12, 2026, 2:14 p.m. |
Created at: May 3, 2026, 4:13 p.m.