Triple
T2705021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IUCN Category II |
E59321
|
entity |
| Predicate | classificationScope |
P39732
|
FINISHED |
| Object | site-level 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: site-level protected areas | Statement: [IUCN Category II, classificationScope, site-level protected areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationScope Context triple: [IUCN Category II, classificationScope, site-level protected areas]
-
A.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
B.
subjectMatterScope
Indicates the thematic or topical domain that an action, statement, or resource pertains to or falls within.
-
C.
identificationScope
Indicates the contextual boundary or extent within which an entity is uniquely identified or recognized.
-
D.
classificationTerm
chosen
Indicates that one entity serves as a categorical label or type used to classify or group another entity.
-
E.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda518c58819096c8b67c0f754655 |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.