Triple
T38068135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 空海 |
E950524
|
entity |
| Predicate | 創建に関与した寺院 |
P13905
|
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.
associatedTemple
chosen
Indicates a relationship where one entity is linked or connected to a particular temple, typically as its relevant or related religious site.
-
B.
associatedWithTempleComplex
Indicates a relationship in which an entity is connected or related to a specific temple complex, such as by location, function, use, or historical association.
-
C.
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.
-
D.
associatedReligionBuilding
Indicates that there is a relationship between a religion and a specific building that is connected to, used by, or significant for that religion.
-
E.
associatedShrineComplex
Indicates that one entity is linked or connected to a particular shrine complex, typically through location, function, or religious association.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.