Triple
T25514779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhadrika |
E639474
|
entity |
| Predicate | heardTeaching |
P24257
|
FINISHED |
| Object | Turning of the Wheel of Dharma discourse |
—
|
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: Turning of the Wheel of Dharma discourse | Statement: [Bhadrika, heardTeaching, Turning of the Wheel of Dharma discourse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heardTeaching Context triple: [Bhadrika, heardTeaching, Turning of the Wheel of Dharma discourse]
-
A.
coreTeaching
Indicates that an entity serves as a primary or foundational teaching or instructional activity for another entity.
-
B.
taughtThat
Indicates that one entity provided instruction or education to another entity about a specific subject, skill, or concept.
-
C.
teachingUnit
Indicates that one entity functions as an instructional or educational unit used for teaching another entity.
-
D.
heard
chosen
Indicates that one entity perceived a sound produced by another entity or source through hearing.
-
E.
containsTeachingOf
Indicates that one entity includes, embodies, or presents the teaching, doctrine, or instructional content associated with another entity.
- 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_69f5f8315ef8819094e5a996997bf0d2 |
completed | May 2, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69f468421ba08190880eac99135e5970 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 2:55 p.m.