Triple
T29036868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Smutsia |
E737883
|
entity |
| Predicate | threatStatusOfGenus |
P172145
|
FINISHED |
| Object | most species are threatened or endangered |
—
|
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: most species are threatened or endangered | Statement: [Smutsia, threatStatusOfGenus, most species are threatened or endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threatStatusOfGenus Context triple: [Smutsia, threatStatusOfGenus, most species are threatened or endangered]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
-
C.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
D.
endangermentType
Indicates the specific way or manner in which one entity puts another at risk of harm, loss, or damage.
-
E.
threatCategory
Indicates the classification of a threat according to its type, severity, or nature within a defined risk or security framework.
- F. None of above. chosen
Provenance (4 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_69f077efb3848190b41574e1670f6ae2 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 9:59 a.m.