Triple
T3817536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caspian seal |
E84292
|
entity |
| Predicate | IUCNRedListCategorySystem |
P4569
|
FINISHED |
| Object | IUCN 3.1 |
—
|
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: IUCN 3.1 | Statement: [Caspian seal, IUCNRedListCategorySystem, IUCN 3.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IUCNRedListCategorySystem Context triple: [Caspian seal, IUCNRedListCategorySystem, IUCN 3.1]
-
A.
IUCNStatusSystem
chosen
Indicates the conservation status classification framework used to assign an IUCN threat category to a species or taxon.
-
B.
conservationStatus
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
C.
typeOfConservation
Indicates the specific kind or category of conservation practice, method, or approach that applies to an entity or situation.
-
D.
protectedAreaIUCNCategory
Indicates the specific IUCN management category assigned to a protected area, describing the type and level of its conservation protection.
-
E.
eraClassification
Indicates the historical era or time period into which an entity is categorized or classified.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee74a2bc081909b237df8b1e27653 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.