Triple
T26551422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 福岡県太宰府市 |
E671686
|
entity |
| Predicate | 祭神の性格 |
P160630
|
FINISHED |
| Object | 学問の神を祀る聖地 |
—
|
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: 学問の神を祀る聖地 | Statement: [福岡県太宰府市, 祭神の性格, 学問の神を祀る聖地]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 祭神の性格 Context triple: [福岡県太宰府市, 祭神の性格, 学問の神を祀る聖地]
-
A.
祭祀の例
Indicates a relationship where one entity serves as an example or instance of a ritual offering or sacrificial ceremony performed to honor deities, spirits, or ancestors.
-
B.
義理の息子
Indicates a relationship where someone is another person's son-in-law or stepson, i.e., a son by marriage or through a non-biological parental tie.
-
C.
Seal of the Hands
Indicates a relationship in which something is formally confirmed, authenticated, or bound through the deliberate action or agreement of specific individuals or parties.
-
D.
enshrinesTitleOfHachiman
Indicates that something formally establishes or honors a specific title belonging to Hachiman.
-
E.
guardianShrineOf
Indicates a relationship where one entity serves as a protective or custodial shrine dedicated to another entity.
- F. None of above. chosen
Provenance (4 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f614624c80819084f6febf57f86828 |
completed | May 2, 2026, 3:12 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f6037bf7a081908862a8359be80cf8 |
completed | May 2, 2026, 2 p.m. |
Created at: April 27, 2026, 1:47 a.m.