Triple
T37271633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Pines Forest |
E924528
|
entity |
| Predicate | containsEndangeredSpecies |
P203496
|
FINISHED |
| Object | Houston toad |
—
|
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: Houston toad | Statement: [Lost Pines Forest, containsEndangeredSpecies, Houston toad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsEndangeredSpecies Context triple: [Lost Pines Forest, containsEndangeredSpecies, Houston toad]
-
A.
hasThreatenedSpecies
Indicates that an entity is associated with one or more species that are classified as threatened or at risk of extinction.
-
B.
hasProtectedSpecies
Indicates that the subject contains, supports, or is associated with one or more species that are legally or formally designated as protected.
-
C.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
D.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
E.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related 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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a019037edbc8190bdaec436ac2fcec6 |
completed | May 11, 2026, 8:15 a.m. |
| PD | Predicate disambiguation | batch_6a018fe05a34819080068f588b5ff80c |
completed | May 11, 2026, 8:14 a.m. |
| PDg | Predicate description generation | batch_6a0190370290819096183e9fb7d32cff |
completed | May 11, 2026, 8:15 a.m. |
Created at: May 3, 2026, 4:15 p.m.