Triple
T33197220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakusa district |
E849797
|
entity |
| Predicate | primaryReligionAtMainTemple |
P8490
|
FINISHED |
| Object | Buddhism |
E8459
|
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: Buddhism | Statement: [Asakusa district, primaryReligionAtMainTemple, Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReligionAtMainTemple Context triple: [Asakusa district, primaryReligionAtMainTemple, Buddhism]
-
A.
religiousAffiliationOfMainShrine
Indicates the religion or faith tradition with which the main shrine is affiliated.
-
B.
mainTemple
chosen
Indicates that one entity serves as the primary or central temple associated with another entity.
-
C.
elementRepresentedByMainTemple
Indicates that a particular element is symbolized or embodied by the main temple in a given religious or cultural context.
-
D.
religiousAffiliationOfShrine
Indicates the religious tradition or denomination with which a shrine is associated or dedicated.
-
E.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
- F. None of above.
Provenance (4 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3525c25a888190a80c5544699c90d5 |
completed | June 19, 2026, 11:19 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.