Triple
T35328229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 小五台山 |
E1020250
|
entity |
| Predicate | 保护对象 |
P26861
|
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 a protective relationship where one entity safeguards, preserves, or defends the attributes or properties of another entity.
-
B.
保护状态
Indicates the protective status or conservation level currently applied to an entity (e.g., how strictly it is protected or conserved).
-
C.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
D.
protectedEntity
chosen
Indicates that one entity is safeguarded or defended by another entity or mechanism.
-
E.
安全保障政策
Indicates a relationship where an authority or organization establishes and implements policies and measures to ensure the security and protection of a state or community from threats.
- 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_69f76deacf4481908e7735a5a7715b0a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f79533b88c8190934ec4cb21770e24 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f79104f5b48190a496cdffde8472da |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.