Triple
T5373298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delilah |
E108901
|
entity |
| Predicate | moralSymbolism |
P53261
|
FINISHED |
| Object | symbol of betrayal |
—
|
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: symbol of betrayal | Statement: [Delilah, moralSymbolism, symbol of betrayal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralSymbolism Context triple: [Delilah, moralSymbolism, symbol of betrayal]
-
A.
moralTheme
Indicates that a work, event, or situation embodies or conveys a particular ethical lesson, value, or moral principle.
-
B.
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.
-
C.
moralConcept
chosen
Indicates that one entity represents or embodies a moral or ethical concept in relation to another.
-
D.
derivesMoralityFrom
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
-
E.
moralImplication
Indicates that one situation, action, or state of affairs entails or suggests a particular moral judgment, obligation, or ethical consequence.
- 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_69bd440c77948190aad2a5f39b7b80f5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd88801b188190b9ac35ed89167fa3 |
completed | March 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69bd846172788190969f24bc7503c05e |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:03 p.m.