Triple
T32424602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三井寺 |
E828543
|
entity |
| Predicate | 宗派本山としての管轄 |
P151785
|
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.
宗派本山
chosen
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 or action involving "Benshan," but the predicate alone is too ambiguous to determine a specific relational meaning without additional context.
-
C.
dioceseGovernedEnd
Indicates the point in time or event at which a diocese ceases to be under the governance or authority of a particular governing entity.
-
D.
boundaryManagedBy
Indicates that the defined boundary is overseen, controlled, or administered by a specific managing entity.
-
E.
governsMonasticLineage
Indicates that one entity holds authoritative control or oversight over the continuation, rules, or succession of a particular monastic lineage associated with another entity.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c286ac288190843dac21651babd0 |
completed | May 3, 2026, 3:35 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:54 a.m.