Triple
T12185976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUCN protected area categories I–VI |
E290334
|
entity |
| Predicate | helpsAddress |
P103646
|
FINISHED |
| Object | mislabeling of protected areas |
—
|
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: mislabeling of protected areas | Statement: [IUCN protected area categories I–VI, helpsAddress, mislabeling of protected areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: helpsAddress Context triple: [IUCN protected area categories I–VI, helpsAddress, mislabeling of protected areas]
-
A.
addresses
Indicates that one entity directs speech, communication, or written correspondence specifically toward another entity.
-
B.
address
Indicates that one entity directs spoken or written communication specifically to another entity.
-
C.
locationAddressed
Indicates that a communication, message, or action is specifically directed to or intended for a particular location or address.
-
D.
addressing
Indicates that one entity is directing speech, communication, or attention specifically toward another entity.
-
E.
addressesQuestion
Indicates that one entity responds to, resolves, or directly engages with a question posed by another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69d91a7e0fc081909ec9769231e728a4 |
completed | April 10, 2026, 3:42 p.m. |
Created at: April 8, 2026, 9:50 p.m.