Triple
T34551664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gyōkyō |
E887082
|
entity |
| Predicate | veneratedDeityAtFoundedShrine |
P5455
|
FINISHED |
| Object | Hachiman |
—
|
NE NERFINISHED |
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: Hachiman | Statement: [Gyōkyō, veneratedDeityAtFoundedShrine, Hachiman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: veneratedDeityAtFoundedShrine Context triple: [Gyōkyō, veneratedDeityAtFoundedShrine, Hachiman]
-
A.
foundedAsShrine
Indicates that an entity was originally established or created as a shrine.
-
B.
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).
-
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.
isMostSacredShrineOf
Indicates that one entity is regarded as the holiest or most sacred shrine associated with another entity (such as a deity, religion, or tradition).
-
E.
veneratedAt
chosen
Indicates that an entity is honored, revered, or worshipped at a particular place or institution.
- 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_69f349cff89081908f91e0b064f4833e |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72026dbe08190b72fc3aa9440ff46 |
completed | May 3, 2026, 10:15 a.m. |
| PD | Predicate disambiguation | batch_69f71cc8074c81909ae09bea2acf1a09 |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:02 a.m.