Triple
T15476382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 龍山寺 |
E376790
|
entity |
| Predicate | 中文名 |
P4878
|
FINISHED |
| Object | 艋舺龍山寺 |
E376790
|
NE 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: [龍山寺, 中文名, 艋舺龍山寺]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 艋舺龍山寺 Context triple: [龍山寺, 中文名, 艋舺龍山寺]
-
A.
龍山寺
chosen
龍山寺 is a historic and culturally significant Buddhist temple in Taipei, Taiwan, renowned for its intricate architecture and role as a major religious and tourist landmark.
-
B.
龍安寺
龍安寺 is a Zen Buddhist temple in Kyoto, Japan, renowned for its iconic rock garden and status as a UNESCO World Heritage Site.
-
C.
金剛頂寺
金剛頂寺は、高知県室戸市に位置し、真言宗の寺院として四国八十八箇所霊場の第26番札所となっている古刹です。
-
D.
園城寺
園城寺 is a historic Tendai Buddhist temple complex in Ōtsu, Shiga Prefecture, Japan, renowned for its ancient halls, cultural treasures, and scenic setting near Lake Biwa.
-
E.
Grand Mazu Temple (Tainan)
Grand Mazu Temple (Tainan) is a historic Taiwanese temple dedicated to the sea goddess Mazu, renowned for its traditional architecture and cultural significance in Tainan.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff2d093ccc8190aefc355a837c83f4 |
completed | May 9, 2026, 12:48 p.m. |
Created at: April 10, 2026, 3:34 a.m.