Triple
T21465925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central American transition zone |
E529592
|
entity |
| Predicate | hasFloraOrigin |
P102079
|
FINISHED |
| Object | Holarctic |
—
|
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: Holarctic | Statement: [Central American transition zone, hasFloraOrigin, Holarctic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFloraOrigin Context triple: [Central American transition zone, hasFloraOrigin, Holarctic]
-
A.
hasFloraGroup
Indicates that an entity is associated with, contains, or is characterized by a particular group or category of plant life.
-
B.
hasFloralRegion
chosen
Indicates that one entity possesses or is associated with a specific floral region as a characteristic or component.
-
C.
hasPlantOriginDiversity
Indicates that something exhibits a variety of origins or sources specifically related to plants or plant-based materials.
-
D.
hasFloralFeature
Indicates that an entity possesses a specific floral characteristic, structure, or attribute.
-
E.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9f32b5c8190bfa5acb3c9b1ab3b |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.