Triple
T38700126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buddha’s flower sermon and silent smile |
E950116
|
entity |
| Predicate | transmissionTo |
P4163
|
FINISHED |
| Object | Mahākāśyapa |
—
|
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: Mahākāśyapa | Statement: [Buddha’s flower sermon and silent smile, transmissionTo, Mahākāśyapa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transmissionTo Context triple: [Buddha’s flower sermon and silent smile, transmissionTo, Mahākāśyapa]
-
A.
transmission
chosen
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
-
B.
transmitsVia
Indicates that something is conveyed, sent, or carried from one entity to another through a specified medium, channel, or mechanism.
-
C.
transmittedWith
Indicates that something is passed or conveyed using a specified medium, method, or channel.
-
D.
laterTransmission
Indicates that one transmission event occurs after another in time.
-
E.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:33 p.m.