Triple
T34940312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 王屋山 |
E1007696
|
entity |
| Predicate | 主要文化资源 |
P81632
|
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.
culturalType
chosen
Indicates the classification of something according to its cultural category, style, or tradition.
-
B.
culturalFoundationFor
Indicates that one entity provides the cultural basis, background, or supporting context that underlies or enables another entity.
-
C.
culturalHeritageIncludes
Indicates that a cultural heritage entity encompasses, contains, or incorporates another cultural element, tradition, artifact, or practice as part of its overall heritage.
-
D.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
-
E.
culturalHeritagePromoted
Indicates that efforts or actions are undertaken to support, publicize, or enhance the visibility and appreciation of a particular cultural heritage.
- 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.