Triple
T36380506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gomortegaceae |
E896031
|
entity |
| Predicate | endemicRegionOfBestKnownSpecies |
P29821
|
FINISHED |
| Object | Chile |
E203
|
NE 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: Chile | Statement: [Gomortegaceae, endemicRegionOfBestKnownSpecies, Chile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endemicRegionOfBestKnownSpecies Context triple: [Gomortegaceae, endemicRegionOfBestKnownSpecies, Chile]
-
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.
naturalRegionOf
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
D.
zoogeographicRegion
Indicates the zoogeographic region in which an organism or taxon naturally occurs or is distributed.
-
E.
biogeographicallyRelatedTo
Indicates that two entities are connected through their biogeographic characteristics, such as shared distribution patterns, regions, or historical biogeographic processes.
- F. None of above.
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_69f76e51d358819092bbc5f119f49476 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7bb3ff1b08190802b1063d55d3923 |
completed | May 3, 2026, 9:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b430ad1c8190b608d2fd9c0c014a |
completed | June 22, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f7b9a611a081908dd6aec1df3f4d7f |
completed | May 3, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:10 p.m.