Triple
T7768367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meadow Valley Range Wilderness |
E179006
|
entity |
| Predicate | mechanizedUse |
P30680
|
FINISHED |
| Object | prohibited within wilderness |
—
|
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: prohibited within wilderness | Statement: [Meadow Valley Range Wilderness, mechanizedUse, prohibited within wilderness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanizedUse Context triple: [Meadow Valley Range Wilderness, mechanizedUse, prohibited within wilderness]
-
A.
motorizedUse
chosen
Indicates that an entity is used or operated by means of a motor or engine, rather than by human or animal power.
-
B.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
E.
civilianUse
Indicates that something is intended for, suitable for, or actually used by civilians rather than military or combat purposes.
- 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_69c69f30602c819082ab52cd4af5c592 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c70435b7f88190a5e68e6ae701c58f |
completed | March 27, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69c7016f4ce881909c2e9f610255187b |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:11 p.m.