Triple
T12185994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUCN Category Ia |
E290335
|
entity |
| Predicate | restrictsActivity |
P47306
|
FINISHED |
| Object | resource extraction |
—
|
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: resource extraction | Statement: [IUCN Category Ia, restrictsActivity, resource extraction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: restrictsActivity Context triple: [IUCN Category Ia, restrictsActivity, resource extraction]
-
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.
activitiesRestricted
Indicates that certain actions or behaviors are limited, prohibited, or constrained under specified conditions or for particular entities.
-
C.
permittedActivity
Indicates that a particular action or behavior is allowed or authorized within a given context or under specified rules.
-
D.
protectedActivity
Indicates that an entity is engaged in an action or behavior that is legally or formally safeguarded from retaliation, interference, or adverse consequences.
-
E.
restrictsFacility
Indicates that one entity imposes limitations or controls on the use, access, or operation of a particular facility.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91a83012c81908d04bbab5fdcd8c2 |
completed | April 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_69d91510a258819090ef8fbdc2d8707b |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:50 p.m.