Triple
T2982043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Compromise with Slavery |
E80533
|
entity |
| Predicate | hasMoralStance |
P29043
|
FINISHED |
| Object | slavery is a sin |
—
|
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: slavery is a sin | Statement: [No Compromise with Slavery, hasMoralStance, slavery is a sin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoralStance Context triple: [No Compromise with Slavery, hasMoralStance, slavery is a sin]
-
A.
hasMoralPerspective
chosen
Indicates that an entity holds or applies a particular moral or ethical viewpoint in evaluating actions, situations, or other entities.
-
B.
hasMoralPurpose
Indicates that an entity, action, or decision is guided by or oriented toward ethical values, principles, or morally significant goals.
-
C.
moralStatus
Indicates the ethical standing or degree of moral consideration that one entity has in relation to another.
-
D.
derivesMoralityFrom
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
-
E.
hasMoralArc
Indicates that something follows a discernible trajectory of moral development, progress, or decline over time.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99a098e08190976eb4b019818f67 |
completed | March 8, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.