Triple
T31399309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | هندوکش شرقی |
E800948
|
entity |
| Predicate | زیستبوم |
P952
|
FINISHED |
| Object | زیستبوم کوهستانی سرد |
—
|
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: زیستبوم کوهستانی سرد | Statement: [هندوکش شرقی, زیستبوم, زیستبوم کوهستانی سرد]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: زیستبوم Context triple: [هندوکش شرقی, زیستبوم, زیستبوم کوهستانی سرد]
-
A.
biome
chosen
Indicates the type of ecological environment or habitat in which an entity naturally exists or is situated.
-
B.
ecozone
Indicates that two entities stand in a biogeographical relationship where one is an ecological zone (ecozone) that characterizes or contains the other.
-
C.
محیط زیست
Indicates a relationship involving the natural environment, such as the impact of actions on ecological systems, resources, and living conditions.
-
D.
biota
Indicates the presence or composition of living organisms (flora, fauna, or other life forms) associated with a given entity or environment.
-
E.
partOfEcosystem
Indicates that an entity functions as a component within a larger ecological system, contributing to and affected by its interactions and processes.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.