Triple
T32444619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngozumpa Cho |
E829108
|
entity |
| Predicate | hasReligionInSurroundingCommunities |
P109600
|
FINISHED |
| Object | Buddhism |
E8459
|
NE 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: Buddhism | Statement: [Ngozumpa Cho, hasReligionInSurroundingCommunities, Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionInSurroundingCommunities Context triple: [Ngozumpa Cho, hasReligionInSurroundingCommunities, Buddhism]
-
A.
localReligion
chosen
Indicates that a particular religion is practiced or holds significance within a specific local area or community.
-
B.
hasReligiousOrganization
Indicates that an entity is associated with, governed by, or belongs to a specific religious organization.
-
C.
sharesReligionWith
Indicates that two entities follow or are associated with the same religion or religious tradition.
-
D.
hasNotableReligiousCommunity
Indicates that an entity is known for having a significant or prominent religious community associated with it.
-
E.
hasFormerReligiousCommunity
Indicates that an entity previously belonged to a particular religious community but is no longer a member of it.
- F. None of above.
Provenance (4 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0238010fa481909b07a5c22aa0abde |
completed | May 11, 2026, 8:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a344f2f89f08190836855e106878652 |
completed | June 18, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_6a0236cfdcb481908323b67b925c76d9 |
completed | May 11, 2026, 8:06 p.m. |
Created at: May 1, 2026, 12:55 a.m.