Triple
T13397081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trigonobalanus |
E319724
|
entity |
| Predicate | biogeographicStatus |
P109758
|
FINISHED |
| Object | relict taxon |
—
|
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: relict taxon | Statement: [Trigonobalanus, biogeographicStatus, relict taxon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: biogeographicStatus Context triple: [Trigonobalanus, biogeographicStatus, relict taxon]
-
A.
biogeographicZone
Indicates the biogeographic region or ecological zone in which an entity (such as a species or habitat) naturally occurs or is distributed.
-
B.
biogeographicClassificationSystem
Indicates the system or scheme used to classify and organize entities according to their biogeographic regions or distributions.
-
C.
biogeographicRole
Indicates the ecological or distributional role an entity plays within a particular biogeographic context or region.
-
D.
biogeographicallyRelatedTo
Indicates that two entities are connected through their biogeographic characteristics, such as shared distribution patterns, regions, or historical biogeographic processes.
-
E.
geographicDistribution
Indicates the spatial range or area over which something occurs, exists, or is found.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d9e7348190844e11dd6cbd13b0 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
| PDg | Predicate description generation | batch_69dadcce5a808190847f2a7833b67a5a |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 9, 2026, 9:34 p.m.