Triple
T27406809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakōdo-jima |
E692023
|
entity |
| Predicate | natureProtectionStatus |
P67365
|
FINISHED |
| Object | protected area |
—
|
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: protected area | Statement: [Nakōdo-jima, natureProtectionStatus, protected area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: natureProtectionStatus Context triple: [Nakōdo-jima, natureProtectionStatus, protected area]
-
A.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
B.
countryProtectedAreaStatus
chosen
Indicates the legal or administrative protection status that a country assigns to a specific area or region.
-
C.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
D.
typeOfConservation
Indicates the specific kind or category of conservation practice, method, or approach that applies to an entity or situation.
-
E.
stateOfConservation
Indicates the condition or preservation status of an entity, typically in terms of how intact, degraded, or at risk it is.
- 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_69ef5205fc808190ad3efc5525b8e6d6 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 12:31 p.m.