Triple
T37733858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faxiang school |
E940228
|
entity |
| Predicate | mainDoctrinalBasis |
P61907
|
FINISHED |
| Object | Yogācāra |
—
|
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: Yogācāra | Statement: [Faxiang school, mainDoctrinalBasis, Yogācāra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainDoctrinalBasis Context triple: [Faxiang school, mainDoctrinalBasis, Yogācāra]
-
A.
hasDoctrinalBasis
Indicates that one concept, claim, or practice is grounded in, supported by, or derived from a specific doctrine or set of doctrines.
-
B.
doctrinalDomain
Indicates the specific area of doctrine or body of teachings within which a belief, statement, or rule is classified.
-
C.
primaryDoctrine
chosen
Indicates that the object represents the main or foundational doctrine associated with the subject.
-
D.
doctrinalTheme
Indicates that one entity concerns, expresses, or is characterized by a particular doctrinal or theological theme in relation to another.
-
E.
doctrineOf
Indicates a relationship where one entity is the doctrinal teaching, principle, or belief system associated with, derived from, or formally held by 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_69f76edefd048190a32212c5c3919531 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.