Triple
T36066426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 神社本庁 |
E1043243
|
entity |
| Predicate | 管轄対象 |
P808
|
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.
mayHaveJurisdictionOver
Indicates that one authority, entity, or body is potentially empowered to exercise legal or official control over another entity, case, or matter.
-
B.
hasJurisdictionOver
chosen
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
C.
oversawArea
Indicates that one entity had supervisory or managerial responsibility over a particular area, region, or domain associated with another entity.
-
D.
consolidatedJurisdictionOf
Indicates that legal authority or control over multiple areas or cases has been combined and is exercised under a single jurisdiction.
-
E.
coversPrefecture
Indicates that one entity (typically an administrative or service area) geographically includes or extends over the territory of a given prefecture.
- 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_69f76e2fd3248190b900d9a492bf5a7a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.