Triple
T6015038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Basin Desert |
E133929
|
entity |
| Predicate | dominantPlantGenus |
P12304
|
FINISHED |
| Object | Artemisia |
—
|
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: Artemisia | Statement: [Great Basin Desert, dominantPlantGenus, Artemisia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantPlantGenus Context triple: [Great Basin Desert, dominantPlantGenus, Artemisia]
-
A.
dominantPlantFamily
Indicates that one plant family is the most prevalent or ecologically dominant group within a specified area, community, or context.
-
B.
famousPlants
Indicates that the plants in question are widely known or celebrated, typically for their distinctive characteristics, history, or cultural significance.
-
C.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
-
D.
notableGenus
chosen
Indicates that one entity is a genus that is especially prominent, well-known, or significant in relation to the other entity.
-
E.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f80ec108190ae9711727debb061 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.