Triple
T8466845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fortification Range |
E200183
|
entity |
| Predicate | typicalEcosystem |
P952
|
FINISHED |
| Object | Great Basin high desert |
—
|
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: Great Basin high desert | Statement: [Fortification Range, typicalEcosystem, Great Basin high desert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEcosystem Context triple: [Fortification Range, typicalEcosystem, Great Basin high desert]
-
A.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
-
B.
primaryEcosystem
Indicates the main type of ecosystem in which an entity predominantly exists or operates.
-
C.
ecosystemRepresentation
Indicates that one entity serves as a model, depiction, or abstraction of an ecosystem, capturing its components, structure, or dynamics.
-
D.
ecoregion
Indicates that one entity is located within, associated with, or belongs to the same ecological region as another entity.
-
E.
biome
chosen
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
- 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_69ca831a4f348190bfdd09250e86ae35 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4d2eb648190b606411eb6a8f7ea |
completed | March 31, 2026, 3:14 p.m. |
| PD | Predicate disambiguation | batch_69cbd10072cc819084be1ed9ac7ebe9d |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:11 p.m.