Triple
T13492356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nijūnisha |
E320666
|
entity |
| Predicate | hasMember |
P10
|
FINISHED |
| Object | Usa Jingū |
E187539
|
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: Usa Jingū | Statement: [Nijūnisha, hasMember, Usa Jingū]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Usa Jingū Context triple: [Nijūnisha, hasMember, Usa Jingū]
-
A.
Usa Jingū
chosen
Usa Jingū is a prominent Shinto shrine in Ōita Prefecture, Japan, revered as the principal sanctuary of the war and guardian deity Hachiman and a historically important religious center.
-
B.
Jingū
Jingū is the formal name for the Ise Grand Shrine, Japan’s most sacred Shinto shrine dedicated primarily to the sun goddess Amaterasu.
-
C.
Taihō
Taihō was a Japanese era (nengō) of the early 8th century, notable for major governmental reforms such as the Taihō Code that helped shape the ritsuryō state.
-
D.
Taga Taisha
Taga Taisha is a prominent Shinto shrine in Taga, Shiga Prefecture, revered for its long history and association with deities of longevity and good fortune.
-
E.
Kujō
Kujō is a Japanese surname historically associated with an aristocratic kuge family that was part of the influential Fujiwara clan.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf4c66008190b287e0551889d7c8 |
completed | April 12, 2026, 2:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7463d3a948190aab07a25fd903d4e |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 9, 2026, 9:43 p.m.