Triple
T2609987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Precepts |
E58749
|
entity |
| Predicate | undertakenBy |
P30855
|
FINISHED |
| Object | lay followers at ceremonies |
—
|
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: lay followers at ceremonies | Statement: [Five Precepts, undertakenBy, lay followers at ceremonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undertakenBy Context triple: [Five Precepts, undertakenBy, lay followers at ceremonies]
-
A.
isConductedBy
chosen
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or entity.
-
B.
undertook
Indicates that an entity assumed responsibility for starting and carrying out a task, project, or action.
-
C.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
D.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
E.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular 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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd89325308190985598373eb0d296 |
completed | March 7, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_69abd80cd7fc81909e9696db2919129f |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.