Triple
T6689489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilderness Study Area |
E152586
|
entity |
| Predicate | mayRestrict |
P47306
|
FINISHED |
| Object | new surface-disturbing activities |
—
|
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: new surface-disturbing activities | Statement: [Wilderness Study Area, mayRestrict, new surface-disturbing activities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayRestrict Context triple: [Wilderness Study Area, mayRestrict, new surface-disturbing activities]
-
A.
mayRestrictActivity
chosen
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
B.
mayNot
Indicates that an entity is not permitted or is prohibited from performing a particular action or entering into a specified relationship.
-
C.
mayReject
Indicates that one entity has the authority or option to refuse, decline, or not accept another entity or proposal.
-
D.
mayHold
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
E.
notRestrictedBy
Indicates that something is free from limitations, constraints, or prohibitions imposed by another entity or condition.
- 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_69c6880687b08190805278b504d1c92c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cd0fa5188190a23281cb09d98139 |
completed | March 27, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69c6ad0d3c1081908dadff7a6a054123 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:04 p.m.