Triple
T32424595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 三井寺 |
E828543
|
entity |
| Predicate | 宗派上の特徴 |
P83342
|
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.
religiousCharacteristic
Indicates that one entity has a religious attribute, quality, or affiliation that characterizes or distinguishes it in a religious context.
-
B.
spiritualityCharacteristic
Indicates that one entity possesses, exhibits, or is defined by a spiritual quality, trait, or aspect in relation to another.
-
C.
traditionCharacteristic
Indicates that a particular quality, feature, or attribute is characteristic of, or typically associated with, a given tradition.
-
D.
religiousSceneSpecialization
Indicates a relationship where a scene is specifically characterized or classified by a particular religious theme, context, or function.
-
E.
denominationalCharacter
chosen
Indicates the specific religious denomination or sect with which an entity is affiliated or characterized.
- 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.