Triple
T3289159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan Baker |
E69058
|
entity |
| Predicate | hasMoralCharacteristic |
P47751
|
FINISHED |
| Object | morally ambiguous |
—
|
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: morally ambiguous | Statement: [Jordan Baker, hasMoralCharacteristic, morally ambiguous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoralCharacteristic Context triple: [Jordan Baker, hasMoralCharacteristic, morally ambiguous]
-
A.
hasMoralPerspective
Indicates that an entity holds or applies a particular moral or ethical viewpoint in evaluating actions, situations, or other entities.
-
B.
hasMoralFunction
Indicates that an entity serves or fulfills a role related to moral or ethical considerations.
-
C.
hasMoralPurpose
Indicates that an entity, action, or decision is guided by or oriented toward ethical values, principles, or morally significant goals.
-
D.
derivesMoralityFrom
Indicates that one entity bases or grounds its moral principles, judgments, or ethical framework on another entity.
-
E.
moralStatus
Indicates the ethical standing or degree of moral consideration that one entity has in relation to another.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb05a3e5c819082552a7a911e3230 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:10 p.m.