Triple
T25514848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Migadāya |
E639477
|
entity |
| Predicate | significanceInBuddhism |
P101707
|
FINISHED |
| Object | site of the Buddha’s first sermon |
—
|
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: site of the Buddha’s first sermon | Statement: [Migadāya, significanceInBuddhism, site of the Buddha’s first sermon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: significanceInBuddhism Context triple: [Migadāya, significanceInBuddhism, site of the Buddha’s first sermon]
-
A.
equivalentInBuddhism
Indicates that one concept, figure, or element is regarded as the corresponding or matching counterpart within the context of Buddhism.
-
B.
statusInBuddhism
chosen
Indicates the recognized role, standing, or significance an entity holds within Buddhist doctrine, practice, or community.
-
C.
viewOnBuddhism
Indicates the stance, opinion, or perspective that an entity holds regarding Buddhism.
-
D.
significanceInTheology
Indicates the importance or influence that something holds within theological beliefs, doctrines, or religious thought.
-
E.
ritualSignificance
Indicates that something holds special importance or meaning within a ritual or ceremonial context.
- 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_69e75dbe32e48190a62d749a0ff2a96a |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 2:55 p.m.