Triple
T26156882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japanese Orthodox Church |
E659988
|
entity |
| Predicate | missionaryOrigin |
P31002
|
FINISHED |
| Object | Russian Orthodox Church |
—
|
NE NERFINISHED |
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: Russian Orthodox Church | Statement: [Japanese Orthodox Church, missionaryOrigin, Russian Orthodox Church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionaryOrigin Context triple: [Japanese Orthodox Church, missionaryOrigin, Russian Orthodox Church]
-
A.
missionaryRegion
Indicates that an entity carries out or is associated with missionary activities within a specified geographic region.
-
B.
sentAsMissionaryBy
Indicates that one entity is formally commissioned and dispatched by another entity to serve as a missionary.
-
C.
missionaryInfluenceFrom
chosen
Indicates that one entity exerts religious or missionary influence upon another entity or location.
-
D.
missionaryOrganization
Indicates that an entity is a religious or faith-based organization dedicated to missionary work or activities.
-
E.
foundedAsMissionFor
Indicates that one entity was originally established as a mission specifically intended to serve or support another entity.
- 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_69ee5bc5a9908190899d39ce95c6d215 |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f60c10f82c8190a102d95ec1941efc |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:28 p.m.