Triple
T34940320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 王屋山 |
E1007696
|
entity |
| Predicate | 生态环境 |
P174308
|
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.
生态定位
Indicates the ecological role or niche an organism occupies within its environment, including its functional position and interactions in the ecosystem.
-
B.
محیط زیست
Indicates a relationship involving the natural environment, such as the impact of actions on ecological systems, resources, and living conditions.
-
C.
environmentTheme
chosen
Indicates that one entity thematically concerns or focuses on environmental topics or issues in relation to another entity.
-
D.
environmentalFocus
Indicates a relationship where an entity prioritizes or concentrates on environmental issues, impacts, or sustainability in its actions or policies.
-
E.
environmentalIssue
Indicates that something is a problem or concern related to the natural environment, such as harm, risk, or negative impact on ecosystems or resources.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.