Triple
T23905908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Regions |
E601197
|
entity |
| Predicate | religionsTransmitted |
P59381
|
FINISHED |
| Object | Buddhism |
—
|
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: Buddhism | Statement: [Western Regions, religionsTransmitted, Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionsTransmitted Context triple: [Western Regions, religionsTransmitted, Buddhism]
-
A.
religiousTransmission
chosen
Indicates the passing on or spread of religious beliefs, practices, or traditions from one entity to another.
-
B.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
C.
promotedReligion
Indicates that an entity actively supported, advocated for, or worked to spread a particular religion.
-
D.
religionAccordingToTradition
Indicates that an entity’s religion is identified or classified according to a particular tradition or customary understanding, rather than strictly formal or official criteria.
-
E.
ethnicReligion
Indicates that a religion is closely associated with a particular ethnic group, often tied to that group’s culture, ancestry, or identity.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce91144c8190b894e25a45dfd7c9 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:35 p.m.