Triple
T10707474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asakusa Shrine |
E252443
|
entity |
| Predicate | mainDeitiesType |
P9989
|
FINISHED |
| Object | kami of Sensō-ji founders |
—
|
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: kami of Sensō-ji founders | Statement: [Asakusa Shrine, mainDeitiesType, kami of Sensō-ji founders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDeitiesType Context triple: [Asakusa Shrine, mainDeitiesType, kami of Sensō-ji founders]
-
A.
mainDeity
Indicates that one entity serves as the primary or chief deity worshiped, revered, or associated with another entity (such as a religion, temple, or culture).
-
B.
deityCategory
Indicates that one entity is classified as belonging to a particular category or type of deity in relation to another entity.
-
C.
typeOfDeity
chosen
Indicates that one entity is classified as a specific kind or category of deity in relation to another.
-
D.
mainDeityForm
Indicates that one entity is the primary or canonical divine form or manifestation of another deity.
-
E.
hasNumberOfDeities
Indicates the specific count of deities associated with an entity, such as a religion, mythology, or belief system.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fde080d48190830eaa863aad61ff |
completed | April 9, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:12 p.m.