Triple
T32765853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Creek Range Wilderness |
E837892
|
entity |
| Predicate | designatedAsWildernessUnder |
P17283
|
FINISHED |
| Object | Wilderness Act of 1964 |
—
|
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: Wilderness Act of 1964 | Statement: [Shell Creek Range Wilderness, designatedAsWildernessUnder, Wilderness Act of 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedAsWildernessUnder Context triple: [Shell Creek Range Wilderness, designatedAsWildernessUnder, Wilderness Act of 1964]
-
A.
designatedWilderness
chosen
Indicates that an area has been officially classified and protected as wilderness under a formal designation or legal framework.
-
B.
hasWildAndScenicDesignation
Indicates that an area or waterway has been formally designated under a Wild and Scenic protection status.
-
C.
hasWildernessArea
Indicates that one entity possesses, contains, or is associated with a designated wilderness area.
-
D.
wildernessDesignationYear
Indicates the year in which an area was officially designated as wilderness.
-
E.
designatedAsWildlifeRefuge
Indicates that an area has been officially assigned the status and protections of a wildlife refuge.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:13 a.m.