Triple
T21445042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paradise |
E529047
|
entity |
| Predicate | hasMoralCondition |
P47751
|
FINISHED |
| Object | Often reserved for the righteous |
—
|
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: Often reserved for the righteous | Statement: [Paradise, hasMoralCondition, Often reserved for the righteous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoralCondition Context triple: [Paradise, hasMoralCondition, Often reserved for the righteous]
-
A.
hasMoralCode
Indicates that an entity adheres to or is guided by a set of moral principles or ethical rules.
-
B.
hasMoralCharacteristic
chosen
Indicates that an entity possesses a particular moral quality, trait, or ethical attribute.
-
C.
hasMoralComplexity
Indicates that the relationship or action involves nuanced ethical considerations, conflicting values, or ambiguity in determining what is morally right or wrong.
-
D.
hasMoralIssue
Indicates that there exists an ethical concern, dilemma, or conflict associated with the referenced entity or situation.
-
E.
hasMoralFunction
Indicates that an entity serves or fulfills a role related to moral or ethical considerations.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b706fd588190bf397a58976f7d98 |
completed | April 22, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:05 p.m.