Triple
T12649509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | McClain County, Oklahoma |
E302119
|
entity |
| Predicate | hasStateRockFormation |
P106181
|
FINISHED |
| Object | rose rock |
—
|
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: rose rock | Statement: [McClain County, Oklahoma, hasStateRockFormation, rose rock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStateRockFormation Context triple: [McClain County, Oklahoma, hasStateRockFormation, rose rock]
-
A.
hasRockType
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
stateOfFormation
Indicates the jurisdiction or region in which an entity was legally created or organized.
-
D.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
-
E.
commonRockUnit
Indicates that two or more geological features share the same rock unit or lithostratigraphic layer.
- F. None of above. chosen
Provenance (4 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:18 p.m.