Triple
T16728805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 天台宗 |
E406530
|
entity |
| Predicate | 関連する山岳信仰 |
P38502
|
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.
associatedWithMountain
chosen
Indicates a relationship in which something has a connection, link, or relevance to a mountain.
-
B.
associatedWithMountainRange
Indicates a relationship where something is connected or related in some way to a specific mountain range.
-
C.
associatedTemple
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
D.
associatedShrine
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
-
E.
holyMountain
Indicates that a mountain is regarded as sacred or religiously significant within a particular belief system or tradition.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38749baa48190892b2e2b978f6eb6 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:20 a.m.