Triple
T24365982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diablo Formation |
E614193
|
entity |
| Predicate | rockTypeGroup |
P1326
|
FINISHED |
| Object | clastic sedimentary rocks |
—
|
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 sedimentary rocks | Statement: [Diablo Formation, rockTypeGroup, clastic sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockTypeGroup Context triple: [Diablo Formation, rockTypeGroup, clastic sedimentary rocks]
-
A.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
B.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
rockUnit
Indicates a relationship where an entity is classified as, or associated with, a particular geological rock unit.
-
D.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
E.
mineralGroup
Indicates that one entity is classified as a member or subtype of a particular mineral group defined by shared mineralogical characteristics.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2938809f081908abf33edb62ed7f8 |
completed | April 29, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:01 a.m.