Triple
T10596742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arizona transition zone |
E250133
|
entity |
| Predicate | dominantRockTypes |
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: [Arizona transition zone, dominantRockTypes, sedimentary rocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantRockTypes Context triple: [Arizona transition zone, dominantRockTypes, sedimentary rocks]
-
A.
geologicEraDominantRocks
Indicates that a particular type or group of rocks is the most characteristic or prevalent during a given geologic era.
-
B.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
-
C.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
D.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
E.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
- 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5278dacc4819089b759744f100e5f |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d5190a6dfc819088262957551808a1 |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:41 p.m.