Triple
T2609966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Precepts |
E58749
|
entity |
| Predicate | firstPrecept |
P41381
|
FINISHED |
| Object | abstaining from taking life |
—
|
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: abstaining from taking life | Statement: [Five Precepts, firstPrecept, abstaining from taking life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPrecept Context triple: [Five Precepts, firstPrecept, abstaining from taking life]
-
A.
firstTemptation
Indicates the initial instance in which an entity is enticed or urged toward a potentially wrong, risky, or forbidden action.
-
B.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
C.
firstSermonEvent
Indicates the event during which an entity delivers its first sermon.
-
D.
firstCommand
Indicates that one entity is the initial or earliest command issued in a sequence of commands associated with another entity.
-
E.
firstWork
Indicates that the related work is the earliest or initial work created, published, or produced by the entity in question.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69abd891bcd481909af5340a64ff69f9 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:50 p.m.