Triple
T8984959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Española Island |
E214636
|
entity |
| Predicate | hasEndemicSubspecies |
P86171
|
FINISHED |
| Object | Española marine iguana population |
—
|
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: Española marine iguana population | Statement: [Española Island, hasEndemicSubspecies, Española marine iguana population]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEndemicSubspecies Context triple: [Española Island, hasEndemicSubspecies, Española marine iguana population]
-
A.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
B.
hasExtinctSubspecies
Indicates that an entity has at least one subspecies that is extinct.
-
C.
isEndemicGenus
Indicates that a genus naturally occurs only within a specific geographic region and is not found natively elsewhere.
-
D.
subspeciesOf
Indicates that one taxonomic group is a subspecific rank within, and directly derived from, another species.
-
E.
recognizedSubspeciesCount
Indicates the number of subspecies that are formally recognized for a given species or taxon.
- 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_69ca839f76bc8190a4b7123cdd682199 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67ecc5188190a6fb4d5456893121 |
completed | April 1, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:03 p.m.