Triple
T25625083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden Christians of Nagasaki |
E642407
|
entity |
| Predicate | causeOfEmergence |
P694
|
FINISHED |
| Object | ban on Christianity in Japan |
—
|
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: ban on Christianity in Japan | Statement: [Hidden Christians of Nagasaki, causeOfEmergence, ban on Christianity in Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEmergence Context triple: [Hidden Christians of Nagasaki, causeOfEmergence, ban on Christianity in Japan]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
causeStatus
Indicates that one entity brings about, initiates, or is responsible for a particular state or condition in another entity.
-
C.
causeOfDisaster
Indicates that the subject is responsible for bringing about or triggering the specified disaster.
-
D.
primaryCauseCategory
Indicates the main type or classification of cause responsible for an outcome or event.
-
E.
causeOfIllness
Indicates that one entity is the reason or source responsible for another entity’s illness or disease.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 5:08 p.m.