Triple
T38018403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharmaguptaka |
E948555
|
entity |
| Predicate | vinayaType |
P120509
|
FINISHED |
| Object | bhikshu vinaya |
—
|
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: bhikshu vinaya | Statement: [Dharmaguptaka, vinayaType, bhikshu vinaya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vinayaType Context triple: [Dharmaguptaka, vinayaType, bhikshu vinaya]
-
A.
vinayaLanguage
Indicates that the subject uses, is expressed in, or is associated with the Vinaya (Buddhist monastic discipline) as a language or linguistic tradition.
-
B.
vinayaPreservedIn
Indicates that a body of Vinaya (monastic disciplinary rules) is preserved, transmitted, or contained within a particular text, collection, or tradition.
-
C.
inBuddhistCanon
Indicates that something is included within, or recognized as part of, the Buddhist canonical scriptures.
-
D.
typeOfMonk
chosen
Indicates that one entity is a specific kind or category of monk in relation to another entity.
-
E.
Prasannapadā_type
Indicates that something is classified as belonging to the Prasannapadā type, i.e., it stands in a relation of being of the same kind or category as the Prasannapadā.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc4748843c8190931432653be4890c |
completed | May 7, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69fc45646ce481908caf292ff9f06e15 |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 3, 2026, 4:20 p.m.