Triple
T10803968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tehuacán-Cuicatlán Biosphere Reserve |
E254914
|
entity |
| Predicate | hasHighEndemismOf |
P8223
|
FINISHED |
| Object | cacti |
—
|
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: cacti | Statement: [Tehuacán-Cuicatlán Biosphere Reserve, hasHighEndemismOf, cacti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighEndemismOf Context triple: [Tehuacán-Cuicatlán Biosphere Reserve, hasHighEndemismOf, cacti]
-
A.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
hasEndemismLevel
chosen
Indicates the degree to which something is restricted or native to a particular geographic area or region.
-
C.
hasEndemicSubspecies
Indicates that a species has one or more subspecies that are native and restricted to a particular geographic area.
-
D.
isEndemicTo
Indicates that something naturally occurs and is restricted to a particular geographic area or region.
-
E.
biodiversityHotspot
Indicates a location or region that supports exceptionally high levels of biodiversity, often with many endemic or threatened species, and is therefore considered a conservation priority.
- 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_69d6aa61c15c8190a1839550c56e75e1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d73370e7388190885b104fc883456e |
completed | April 9, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69d6f3188f00819094ee8d65b187a333 |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:18 p.m.