Triple
T6774995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lemerig |
E155132
|
entity |
| Predicate | hasEndangermentClassification |
P1339
|
FINISHED |
| Object | moribund |
—
|
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: moribund | Statement: [Lemerig, hasEndangermentClassification, moribund]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndangermentClassification Context triple: [Lemerig, hasEndangermentClassification, moribund]
-
A.
conservationStatus
chosen
Indicates the level of risk or protection category assigned to an entity, typically reflecting how threatened it is with extinction or decline.
-
B.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
C.
hasCriticalDesignation
Indicates that an entity has been assigned a status or label marking it as critical in importance, priority, or required attention.
-
D.
wildlifeProtectionStatus
Indicates the level or type of legal or conservation protection currently applied to wildlife.
-
E.
hasConservationPriority
Indicates that an entity is assigned a particular level or status of importance for conservation or protection efforts.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.