Triple
T16731738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tibetan antelope |
E406606
|
entity |
| Predicate | CITESStatus |
P31440
|
FINISHED |
| Object | Appendix I |
—
|
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: Appendix I | Statement: [Tibetan antelope, CITESStatus, Appendix I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CITESStatus Context triple: [Tibetan antelope, CITESStatus, Appendix I]
-
A.
CITESListing
chosen
Indicates that an entity is included in one of the appendices of the CITES (Convention on International Trade in Endangered Species) regulatory listings, specifying its status and trade restrictions under that framework.
-
B.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
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.
stateOfConservation
Indicates the condition or preservation status of an entity, typically in terms of how intact, degraded, or at risk it is.
-
E.
legalStatusOfItems
Indicates the legal classification or regulatory standing that applies to specified items.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c362bb88190921fab43d76c3ee8 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.