Triple
T2609986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Five Precepts |
E58749
|
entity |
| Predicate | undertakenAs |
P41389
|
FINISHED |
| Object | voluntary training rules |
—
|
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: voluntary training rules | Statement: [Five Precepts, undertakenAs, voluntary training rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undertakenAs Context triple: [Five Precepts, undertakenAs, voluntary training rules]
-
A.
undertook
Indicates that an entity assumed responsibility for starting and carrying out a task, project, or action.
-
B.
workedUnder
Indicates that one entity was hierarchically subordinate to and performed work under the supervision or authority of another entity.
-
C.
plannedUnder
Indicates that one entity has been scheduled, organized, or arranged to occur within the scope, authority, or framework of another entity.
-
D.
underAuspicesOf
Indicates that an action, event, or entity operates under the sponsorship, authority, or guidance of another party.
-
E.
isConductedBy
Indicates that an event, activity, or process is carried out, organized, or overseen by a particular agent or entity.
- 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.