Triple
T5181325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Chile |
E116926
|
entity |
| Predicate | dominantBiome |
P952
|
FINISHED |
| Object | sclerophyllous forest |
—
|
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: sclerophyllous forest | Statement: [Central Chile, dominantBiome, sclerophyllous forest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantBiome Context triple: [Central Chile, dominantBiome, sclerophyllous forest]
-
A.
dominantEnvironment
Indicates the primary or prevailing environment or setting in which an entity most characteristically exists, operates, or exerts influence.
-
B.
biome
chosen
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
C.
hasDominantSpecies
Indicates that one entity possesses or is characterized by a species that is predominant or most influential within it.
-
D.
dominantCommunity
Indicates that one community holds a prevailing or controlling influence, status, or presence over others within a given context.
-
E.
biomeIncludes
Indicates that a biome contains or encompasses a particular entity, such as a species, habitat, or environmental feature, as part of its composition.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd799bc58c819098a8e91e21baaef4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:45 p.m.