Triple
T30155435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江 |
E766507
|
entity |
| Predicate | 生态作用 |
P65595
|
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.
ecologicalRelevance
chosen
Indicates that one entity has significance, impact, or importance for the functioning, stability, or dynamics of another entity’s ecosystem or ecological context.
-
C.
ecosystemRelevance
Indicates the degree to which something is important, impactful, or integral to the functioning or health of a particular ecosystem.
-
D.
立地特性
Indicates the characteristics or qualities of a location that define its situational conditions or advantages in relation to its surroundings.
-
E.
ecoregionInfluence
Indicates that one ecoregion affects or shapes the environmental characteristics, processes, or conditions of another area or system.
- 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:20 p.m.