Triple
T25383972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheriff Logan |
E631469
|
entity |
| Predicate | moralThemeInvolvement |
P25343
|
FINISHED |
| Object | good versus evil |
—
|
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: good versus evil | Statement: [Sheriff Logan, moralThemeInvolvement, good versus evil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralThemeInvolvement Context triple: [Sheriff Logan, moralThemeInvolvement, good versus evil]
-
A.
moralTheme
chosen
Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
-
B.
moralAttitude
Indicates a subject’s evaluative stance or judgment about the moral rightness or wrongness of another entity, action, or situation.
-
C.
moralImplication
Indicates that one situation, action, or state of affairs entails or suggests a particular moral judgment, obligation, or ethical consequence.
-
D.
moralConcept
Indicates that one entity represents or embodies a moral or ethical concept in relation to another.
-
E.
moralAssociation
Indicates a perceived ethical or moral connection between entities, such as one influencing or reflecting the moral character, values, or judgment of the other.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f56566c5408190a8841d2c45dcf52c |
completed | May 2, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:46 p.m.