Triple
T19412835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Habits |
E485631
|
entity |
| Predicate | confrontsTheme |
P91427
|
FINISHED |
| Object | moral responsibility |
—
|
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: moral responsibility | Statement: [Bad Habits, confrontsTheme, moral responsibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confrontsTheme Context triple: [Bad Habits, confrontsTheme, moral responsibility]
-
A.
tacklesTheme
chosen
Indicates that one entity addresses, explores, or deals with a particular theme as a central subject.
-
B.
confronts
Indicates that one entity directly faces and challenges another, often in opposition or dispute.
-
C.
oppositionTheme
Indicates that one entity thematically represents or embodies opposition or conflict in relation to another entity.
-
D.
helpsCharacterConfront
Indicates that one character actively supports or enables another character in facing and dealing with a difficult issue, fear, or challenge.
-
E.
undergoesTheme
Indicates that an entity experiences or is subjected to a process, event, or change described by another entity or action.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af77eb481909fcfb6cdde1e8580 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.