Triple
T16059453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chisan-ha |
E389567
|
entity |
| Predicate | hasMonasticDiscipline |
P1772
|
FINISHED |
| Object | Vinaya-based precepts |
—
|
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: Vinaya-based precepts | Statement: [Chisan-ha, hasMonasticDiscipline, Vinaya-based precepts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonasticDiscipline Context triple: [Chisan-ha, hasMonasticDiscipline, Vinaya-based precepts]
-
A.
hasClericalDiscipline
chosen
Indicates that an entity is subject to, or governed by, a particular set of clerical or religious disciplinary rules or practices.
-
B.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
C.
monasticRequirement
Indicates that one entity imposes, specifies, or embodies a rule, obligation, or condition that must be fulfilled within a monastic or religious order.
-
D.
hasMonasticName
Indicates that an entity possesses a specific name adopted or assigned within a monastic or religious order.
-
E.
hasAsceticType
Indicates that an entity is associated with or characterized by a specific form or type of ascetic practice or lifestyle.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1858a00888190b8505071575dc56f |
completed | April 17, 2026, 12:57 a.m. |
| PD | Predicate disambiguation | batch_69e18272f2288190a17d45fb01cc2b07 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:57 a.m.