Triple
T3226818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 淵田 美津雄 |
E67642
|
entity |
| Predicate | 改宗前の宗教的背景 |
P111
|
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.
formerReligiousAffiliation
chosen
Indicates that an entity previously adhered to a particular religion or religious denomination but no longer does so.
-
B.
convertedToReligion
Indicates that an entity adopted or changed to a particular religion, typically from a previous belief system or lack thereof.
-
C.
religiousBackgroundOfBase
Indicates the religious background or affiliation associated with a given base or primary entity.
-
D.
previousReligionOfKingdom
Indicates that a specified religion was formerly practiced or officially adopted by a kingdom before being replaced or superseded.
-
E.
religionBeforeReformation
Indicates that an entity’s religious affiliation or practice existed or was established prior to the historical period known as the Reformation.
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb5e67c819082070d108d3613ba |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.