Triple
T4304887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Valley |
E99929
|
entity |
| Predicate | rockhoundingRegulations |
P18323
|
FINISHED |
| Object | BLM rules apply |
—
|
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: BLM rules apply | Statement: [Virgin Valley, rockhoundingRegulations, BLM rules apply]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockhoundingRegulations Context triple: [Virgin Valley, rockhoundingRegulations, BLM rules apply]
-
A.
climbingRegulations
Indicates rules or restrictions governing how climbing activities may be conducted in a given area or context.
-
B.
recreationRegulation
chosen
Indicates rules, restrictions, or guidelines governing recreational activities or leisure use of a place or resource.
-
C.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
D.
recreationAccess
Indicates that one entity provides or has the ability to use recreational facilities, activities, or spaces associated with another entity.
-
E.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
- 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_69b345528ebc8190b5abc7e95094792d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350b8e1cc819094ce3d6f6c8da767 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b347ff45cc8190b0cc335a94cc3d73 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:09 p.m.