Triple
T7486823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNASPE |
E176901
|
entity |
| Predicate | includesManagementCategory |
P70092
|
FINISHED |
| Object | strict protection 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: strict protection areas | Statement: [SNASPE, includesManagementCategory, strict protection areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesManagementCategory Context triple: [SNASPE, includesManagementCategory, strict protection areas]
-
A.
managementIncludes
Indicates that a management entity encompasses, oversees, or has responsibility for the included entity or entities.
-
B.
hasManagement
Indicates that one entity exercises managerial authority or oversight over another entity.
-
C.
hasManagementRelevance
Indicates that something is pertinent or significant to management activities, decisions, or responsibilities.
-
D.
classificationTypeManaged
Indicates that the classification type is controlled or administered through a managed process or system rather than being assigned freely or ad hoc.
-
E.
containsCategory
chosen
Indicates that one entity includes or encompasses a specific category as part of its classification or organizational structure.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5582adc81908b68439762965d88 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.