Triple
T27011022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pisba páramo |
E680382
|
entity |
| Predicate | endemicSpeciesPresence |
P954
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pisba páramo, endemicSpeciesPresence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endemicSpeciesPresence Context triple: [Pisba páramo, endemicSpeciesPresence, yes]
-
A.
hasEndemicSpecies
chosen
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
areEndangeredIn
Indicates that the entities are classified as endangered within a specified geographic area or jurisdiction.
-
C.
hasNativeSpecies
Indicates that a particular species naturally occurs and evolved in a specified geographic area or habitat, rather than being introduced from elsewhere.
-
D.
areEndangeredInPart
Indicates that an entity is endangered only in certain regions or parts of its overall range, rather than throughout its entire distribution.
-
E.
hasEndemismLevel
Indicates the degree to which something is restricted or native to a particular geographic area or region.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f621d6eeb8819091c42b69b26b4d8a |
completed | May 2, 2026, 4:09 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:03 a.m.