Triple
T17160845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tararua Forest Park |
E416472
|
entity |
| Predicate | protectsSpeciesType |
P77745
|
FINISHED |
| Object | native birds |
—
|
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: native birds | Statement: [Tararua Forest Park, protectsSpeciesType, native birds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsSpeciesType Context triple: [Tararua Forest Park, protectsSpeciesType, native birds]
-
A.
protectsEcosystemType
Indicates that one entity safeguards, preserves, or maintains the health and integrity of a particular type of ecosystem.
-
B.
conservationFocusSpecies
Indicates that a conservation effort, program, or context is specifically directed toward or centered on a particular species.
-
C.
hasProtectedSpecies
chosen
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
D.
typeOfConservation
Indicates the specific kind or category of conservation practice, method, or approach that applies to an entity or situation.
-
E.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f911114481909c865b2e2d3b3a2b |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.