Triple
T4216065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nesiota elliptica |
E94218
|
entity |
| Predicate | isEndemic |
P29821
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nesiota elliptica, isEndemic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndemic Context triple: [Nesiota elliptica, isEndemic, true]
-
A.
isEndemicTo
chosen
Indicates that something naturally occurs and is restricted to a particular geographic area or region.
-
B.
hasEndemicSpecies
Indicates that a place or region contains species that are native to and found only within that specific geographic area.
-
C.
endemicLegacy
Indicates that a condition, trait, or influence is persistently rooted and locally confined to a particular context, region, or population as a lasting effect.
-
D.
initiallyEndemicCountries
Indicates the set of countries in which something (typically a disease or species) was originally endemic at the start of the period or process being considered.
-
E.
isReservoirOf
Indicates that one entity serves as a storage source or container holding a particular substance, resource, or quantity for another entity or purpose.
- 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_69b3451997e08190851db4a9a588837d |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.