Triple
T30885837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jōjitsu school |
E786759
|
entity |
| Predicate | doctrinalRoot |
P146915
|
FINISHED |
| Object | Abhidharma |
—
|
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: Abhidharma | Statement: [Jōjitsu school, doctrinalRoot, Abhidharma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doctrinalRoot Context triple: [Jōjitsu school, doctrinalRoot, Abhidharma]
-
A.
doctrinalDomain
Indicates the specific area of doctrine or body of teachings within which a belief, statement, or rule is classified.
-
B.
theologicalRoot
chosen
Indicates that something originates from, is fundamentally based on, or is primarily explained by theological principles, doctrines, or beliefs.
-
C.
doctrinalTheme
Indicates that one entity concerns, expresses, or is characterized by a particular doctrinal or theological theme in relation to another.
-
D.
doctrinalTerm
Indicates that one entity is a doctrinal or theological term that conceptually characterizes, labels, or defines the other entity within a religious or ideological system.
-
E.
sharesDoctrinalRootsWith
Indicates that two entities originate from or are based on the same or closely related doctrinal or ideological foundations.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6953bafb88190a860e9c68a3dd4b2 |
completed | May 3, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 29, 2026, 8:49 p.m.