Triple
T2610064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangha |
E58751
|
entity |
| Predicate | coreRoleInBuddhism |
P9873
|
FINISHED |
| Object | field of merit |
—
|
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: field of merit | Statement: [Sangha, coreRoleInBuddhism, field of merit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreRoleInBuddhism Context triple: [Sangha, coreRoleInBuddhism, field of merit]
-
A.
roleInMonasticism
Indicates the specific function, position, or status an entity holds within a monastic community or tradition.
-
B.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
C.
theologicalRole
chosen
Indicates a relationship where an entity holds or is assigned a specific function, office, or status within a theological or religious framework.
-
D.
roleInJudaism
Indicates the specific religious, social, or institutional function an entity holds within the context of Judaism.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.