Triple
T38018395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dharmaguptaka |
E948555
|
entity |
| Predicate | monasticCodeUsedIn |
P41378
|
FINISHED |
| Object | China |
—
|
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: China | Statement: [Dharmaguptaka, monasticCodeUsedIn, China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monasticCodeUsedIn Context triple: [Dharmaguptaka, monasticCodeUsedIn, China]
-
A.
monasticCode
chosen
Indicates that an entity follows, is governed by, or is associated with a specific set of monastic rules or disciplinary code.
-
B.
monasticModel
Indicates a relationship where one entity serves as a pattern, example, or standard of monastic life or practice for another entity.
-
C.
monasticComponent
Indicates that something is a structural or functional part of a monastic institution or community.
-
D.
hasMonasticHistory
Indicates that an entity has a historical association with monastic life, institutions, or traditions.
-
E.
monasticTradition
Indicates that an entity follows, belongs to, or is characterized by a particular monastic rule, lineage, or way of religious life.
- 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_69fbc995dc2481908b3bd4217f8101e7 |
completed | May 6, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ee04f08190977b7ad70fc85896 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:20 p.m.