Triple
T14886772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shoin Jinja |
E350144
|
entity |
| Predicate | hasEnshrinedDeity |
P5606
|
FINISHED |
| Object | spirit of Yoshida Shōin |
—
|
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: spirit of Yoshida Shōin | Statement: [Shoin Jinja, hasEnshrinedDeity, spirit of Yoshida Shōin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEnshrinedDeity Context triple: [Shoin Jinja, hasEnshrinedDeity, spirit of Yoshida Shōin]
-
A.
patronDeityOf
Indicates that one entity serves as the protective or primary deity associated with, worshipped by, or presiding over another entity (such as a person, group, or place).
-
B.
hasDeity
chosen
Indicates that one entity recognizes, worships, or is associated with another entity as its deity or divine figure.
-
C.
stateShrineOf
Indicates that one entity is officially designated as a state-recognized shrine associated with or located within another entity (typically a state or region).
-
D.
hasConsortDeity
Indicates that one deity is the consort (spouse or intimate divine partner) of another deity.
-
E.
servedDeity
Indicates that one entity acted in service, devotion, or worship toward a particular deity.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5f5b1c88190815f3585770cb135 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:56 a.m.