Triple
T36925702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fountain Formation |
E913336
|
entity |
| Predicate | grainSizeRange |
P97532
|
FINISHED |
| Object | from conglomerate to fine sandstone and siltstone |
—
|
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: from conglomerate to fine sandstone and siltstone | Statement: [Fountain Formation, grainSizeRange, from conglomerate to fine sandstone and siltstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grainSizeRange Context triple: [Fountain Formation, grainSizeRange, from conglomerate to fine sandstone and siltstone]
-
A.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
-
B.
clusterSizeRange
Indicates the range of allowable or observed sizes for a given cluster within a specified context.
-
C.
grainShape
Indicates the characteristic form or contour of a grain or granular particle.
-
D.
typicalSedimentSizeRange
chosen
Indicates the usual range of sediment particle sizes associated with an entity or environment.
-
E.
rangeSize
Indicates the extent or magnitude of the range over which something applies, varies, or is distributed.
- 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_69f9fde1fbf881909e5474d99404cdfc |
completed | May 5, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.