Triple
T26156872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Orthodox Church |
E659988
|
entity |
| Predicate | primaryLanguageOfEvangelization |
P194408
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Japanese Orthodox Church, primaryLanguageOfEvangelization, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryLanguageOfEvangelization Context triple: [Japanese Orthodox Church, primaryLanguageOfEvangelization, Japanese]
-
A.
hasEvangelizationFocus
Indicates that an entity is oriented toward or primarily concerned with evangelization activities or objectives.
-
B.
mainEvangelist
Indicates that one entity serves as the primary or leading proponent, promoter, or advocate for another entity.
-
C.
languageOfGospelTraditionally
Indicates the language in which a particular Gospel is traditionally believed or held to have been written or transmitted.
-
D.
languageOfWorship
Indicates the language in which religious worship, rituals, or liturgical practices are conducted.
-
E.
missionizationAt
Indicates the location or context in which a missionizing or religious conversion effort takes place.
- F. None of above. chosen
Provenance (4 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
| PDg | Predicate description generation | batch_69fd6f9a8bd881909983fe8f4cd0ba98 |
completed | May 8, 2026, 5:07 a.m. |
Created at: April 26, 2026, 8:28 p.m.