Triple
T19687680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Purgatory |
E472753
|
entity |
| Predicate | moralStructureBasedOn |
P27668
|
FINISHED |
| Object | seven deadly sins |
—
|
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: seven deadly sins | Statement: [Mount Purgatory, moralStructureBasedOn, seven deadly sins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralStructureBasedOn Context triple: [Mount Purgatory, moralStructureBasedOn, seven deadly sins]
-
A.
derivesMoralityFrom
chosen
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
-
B.
moralBelief
Indicates that an agent holds a normative judgment about what is right, wrong, good, or bad in a given context.
-
C.
moralCriterion
Indicates that something is being evaluated or classified according to a standard of moral judgment or ethical rightness.
-
D.
moralConcept
Indicates that one entity represents or embodies a moral or ethical concept in relation to another.
-
E.
moralTheme
Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6420d39688190ad3a84dbffce4ffe |
completed | April 20, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.