Triple
T581807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Endangered Species Act |
E15073
|
entity |
| Predicate | protectsCategory |
P4708
|
FINISHED |
| Object | endangered species |
—
|
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: endangered species | Statement: [Endangered Species Act, protectsCategory, endangered species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protectsCategory Context triple: [Endangered Species Act, protectsCategory, endangered species]
-
A.
protectedCategory
chosen
Indicates that one entity is classified under a legally or formally recognized group that is granted special protection from discrimination or adverse treatment.
-
B.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
C.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
D.
protectedAs
Indicates that one entity is safeguarded, preserved, or kept safe by another entity or under a specified protective status or mechanism.
-
E.
aimsToProtect
Indicates an intention or purpose to safeguard or defend one entity, value, or condition from harm, risk, or undesirable outcomes.
- 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_69a4935783b8819082b77726ec10cc42 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49b84899881909d5b2b4e67e22d9b |
completed | March 1, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69a494c7f9008190bd8d05b4dc2a7c7f |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.