Triple
T8856591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siju Wildlife Sanctuary |
E210771
|
entity |
| Predicate | protectionPurpose |
P64472
|
FINISHED |
| Object | conservation of wildlife |
—
|
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: conservation of wildlife | Statement: [Siju Wildlife Sanctuary, protectionPurpose, conservation of wildlife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectionPurpose Context triple: [Siju Wildlife Sanctuary, protectionPurpose, conservation of wildlife]
-
A.
hasProtectionPurpose
chosen
Indicates that something is intended or designed to serve a protective function or goal.
-
B.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protectionCategory
Indicates a classification relationship where an entity is assigned to a specific type or level of protection based on defined protective criteria or rules.
-
D.
protectionReason
Indicates the justification or cause for which protection is provided or required in the relationship between entities.
-
E.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60e259248190abd334bbfcdcb955 |
completed | April 1, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69cc5c279ea481908c71756f694b66bf |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:50 p.m.