Triple
T15476423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 龍山寺 |
E376790
|
entity |
| Predicate | 文化意義 |
P1579
|
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.
isCulturalSignificance
Indicates that something holds notable meaning, value, or influence within a particular culture or cultural context.
-
B.
hasCulturalSignificance
chosen
Indicates that something holds notable meaning, value, or importance within a particular culture or cultural context.
-
C.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
-
D.
culturalKnowledge
Indicates that one entity possesses or conveys understanding of the customs, practices, values, or traditions associated with a particular culture.
-
E.
culturalElements
Indicates a relationship where certain elements (such as practices, symbols, or artifacts) belong to, express, or characterize a particular culture or cultural context.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f88a5dc8190a2d7830748e29180 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded2874b788190999158e0f043be21 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:34 a.m.