Triple
T37913674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 曹洞宗 |
E945751
|
entity |
| Predicate | 宗派本部 |
P20256
|
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 a religious sect or school is associated with, or headquartered at, a particular main temple or principal mountain temple.
-
B.
札所
Indicates a relationship in which a location is designated as a numbered temple or sacred site on a specific pilgrimage route.
-
C.
majorTempleManagingBody
chosen
Indicates that an entity serves as the primary governing or administrative body responsible for managing a major temple.
-
D.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
E.
mainMonasteryLocation
Indicates the place where a religious order’s primary or central monastery is situated.
- 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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.