Triple
T27004810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorikai-shū |
E680212
|
entity |
| Predicate | religiousMovementType |
P186345
|
FINISHED |
| Object | Japanese new religious movement |
—
|
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 new religious movement | Statement: [Gorikai-shū, religiousMovementType, Japanese new religious movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousMovementType Context triple: [Gorikai-shū, religiousMovementType, Japanese new religious movement]
-
A.
religiousMovementLed
Indicates that one entity serves as the leader or guiding figure of a particular religious movement.
-
B.
religiousServiceType
Indicates the specific kind or category of religious service associated with an event or context.
-
C.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
D.
religiousBranchOf
Indicates that one religion, denomination, or sect is a subdivision or offshoot of a larger parent religious tradition.
-
E.
religiousSupportType
Indicates the type or form of support provided or received in a religious or faith-based context.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: April 27, 2026, 7 a.m.