Triple
T35615297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild Mammals (Protection) Act 1996 |
E1029148
|
entity |
| Predicate | subjectOfProtection |
P15826
|
FINISHED |
| Object | wild mammals |
—
|
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: wild mammals | Statement: [Wild Mammals (Protection) Act 1996, subjectOfProtection, wild mammals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfProtection Context triple: [Wild Mammals (Protection) Act 1996, subjectOfProtection, wild mammals]
-
A.
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.
-
B.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
E.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
- 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_69f76e0709408190bbe322bf1707ef6b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: May 3, 2026, 4:05 p.m.