Triple
T24911581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangkum Reastr Niyum |
E623858
|
entity |
| Predicate | usedReligionInIdeology |
P76551
|
FINISHED |
| Object | Theravada 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: Theravada Buddhism | Statement: [Sangkum Reastr Niyum, usedReligionInIdeology, Theravada Buddhism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedReligionInIdeology Context triple: [Sangkum Reastr Niyum, usedReligionInIdeology, Theravada Buddhism]
-
A.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
B.
usedReligionFor
chosen
Indicates that an entity employed religion as a means or tool to achieve some purpose, goal, or effect.
-
C.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
-
D.
religiousAttitude
Indicates an entity’s stance, disposition, or orientation toward religion or religious beliefs.
-
E.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
- 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_69e2fac889c081908e9ff686cb428e5a |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42388b0708190adcdf1ba132b66f8 |
completed | May 1, 2026, 3:52 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:28 a.m.