Triple
T35469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ten Commandments |
E701
|
entity |
| Predicate | ethicalCategory |
P87
|
FINISHED |
| Object | divine command ethics |
—
|
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: divine command ethics | Statement: [Ten Commandments, ethicalCategory, divine command ethics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethicalCategory Context triple: [Ten Commandments, ethicalCategory, divine command ethics]
-
A.
ethicalDebate
Indicates a relationship where parties are engaged in discussing, questioning, or disputing the moral rightness or wrongness of actions, policies, or principles.
-
B.
hasEthicalTeaching
Indicates that one entity provides, promotes, or embodies instruction or guidance related to ethical principles, values, or moral conduct for another entity.
-
C.
conducts
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
D.
category
chosen
Indicates that one entity is classified as a member or type within the grouping or class defined by another entity.
-
E.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a24989c3308190af59dfae37cfc32f |
completed | Feb. 28, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69a24873e97c8190b9e4279e43b6de14 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.