Triple
T22548919
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waterpocket Fold monocline |
E557504
|
entity |
| Predicate | primaryRockTypes |
P1326
|
FINISHED |
| Object | 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: sedimentary rocks | Statement: [Waterpocket Fold monocline, primaryRockTypes, sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRockTypes Context triple: [Waterpocket Fold monocline, primaryRockTypes, sedimentary rocks]
-
A.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
B.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
C.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
D.
geologicEraDominantRocks
Indicates that a particular type or group of rocks is the most characteristic or prevalent during a given geologic era.
-
E.
primaryOreTypes
Indicates the main types of ore that are predominantly associated with or extracted from a given 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f372df48190ae5dd461b1230bc7 |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.