Triple
T14787222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 太庙 |
E347557
|
entity |
| Predicate | 保护意义 |
P39107
|
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.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
B.
reasonForPreservation
chosen
Indicates that something is being preserved or maintained for a particular reason, purpose, or justification.
-
C.
preservationPurpose
Indicates that something exists, is created, or is maintained with the specific aim of preserving or safeguarding another entity or resource.
-
D.
culturalProtectionMechanism
Indicates a relationship where measures, policies, or practices are in place to preserve, safeguard, or defend a culture or its elements from loss, harm, or external pressures.
-
E.
protectsRight
Indicates that one entity safeguards, upholds, or defends the legal or moral rights of another entity.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa083e481908336d58d026eec32 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.