Triple
T3973669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avesta |
E85589
|
entity |
| Predicate | moralConcept |
P53261
|
FINISHED |
| Object | asha |
—
|
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: asha | Statement: [Avesta, moralConcept, asha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moralConcept Context triple: [Avesta, moralConcept, asha]
-
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.
moralImplication
Indicates that one situation, action, or state of affairs entails or suggests a particular moral judgment, obligation, or ethical consequence.
-
D.
moralExpectation
Indicates that one entity is expected, by moral or ethical standards, to behave in a certain way toward another entity or in a given situation.
-
E.
derivesMoralityFrom
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
- F. None of above. chosen
Provenance (4 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefac8f7a48190b065487ce090eaf2 |
completed | March 9, 2026, 4:52 p.m. |
Created at: March 9, 2026, 3:32 p.m.