Triple
T34598323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Rock State Park |
E888378
|
entity |
| Predicate | hasSoilOrRockType |
P1326
|
FINISHED |
| Object | St. Peter Sandstone |
—
|
NE NERFINISHED |
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: St. Peter Sandstone | Statement: [Castle Rock State Park, hasSoilOrRockType, St. Peter Sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSoilOrRockType Context triple: [Castle Rock State Park, hasSoilOrRockType, St. Peter Sandstone]
-
A.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
B.
hasRockType
chosen
Indicates that an entity is composed of, characterized by, or associated with a specific type of rock.
-
C.
hasSoilProperty
Indicates that a soil entity possesses or is characterized by a specific soil-related property or attribute.
-
D.
hasSoilTexture
Indicates that one entity (typically a soil or land area) possesses a specific soil texture classification (such as sandy, loamy, or clayey).
-
E.
hasRegolithBehavior
Indicates that an entity exhibits or is associated with a specific type of behavior related to regolith (loose surface material such as soil, dust, or broken rock).
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 2:03 a.m.