Triple
T22685464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Wolf Recovery Program |
E560898
|
entity |
| Predicate | targetsStatus |
P149240
|
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: [Red Wolf Recovery Program, targetsStatus, endangered species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetsStatus Context triple: [Red Wolf Recovery Program, targetsStatus, endangered species]
-
A.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
B.
targetOSStatus
Indicates the operational or lifecycle state currently associated with the specified target operating system.
-
C.
collectiveStatus
Indicates the overall state or condition shared by a group of entities considered together as a collective.
-
D.
targetsShow
Indicates that one entity is the intended audience or focus of a particular show or presentation.
-
E.
targetsProvision
Indicates that one entity is the intended recipient or beneficiary of a provision, service, or resource supplied by another entity.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178637bc08190a8dfb33b5f4249e5 |
completed | April 29, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:12 p.m.