Triple
T14457931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shendao |
E358503
|
entity |
| Predicate | writtenForm |
P2203
|
FINISHED |
| Object | 神道 |
E4281
|
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: [Shendao, writtenForm, 神道]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: 神道 Context triple: [Shendao, writtenForm, 神道]
-
A.
天神
天神 is a Japanese Shinto deity most commonly associated with scholarship and learning, often identified with the deified scholar Sugawara no Michizane.
-
B.
Shinto Taikyo
Shinto Taikyo is a Shinto religious sect in Japan that emphasizes traditional Shinto rituals and teachings within the broader framework of Sect Shinto.
-
C.
神宮
神宮 is a Japanese term typically referring to a grand Shinto shrine of special significance, often associated with the imperial family or major deities.
-
D.
Shinto Honkyoku
Shinto Honkyoku is a traditional Shinto liturgical component, likely consisting of core ritual texts, chants, or practices central to Sect Shinto worship.
-
E.
Shinto
chosen
Shinto is the indigenous religion of Japan centered on the worship of kami (spirits or deities) and the veneration of nature and ancestors.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd6d890be88190afe61dde0d1e75a8 |
completed | May 8, 2026, 4:58 a.m. |
Created at: April 10, 2026, 1:19 a.m.