Triple
T29098860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Turner |
E735085
|
entity |
| Predicate | ethicallyCharacterizedAs |
P9237
|
FINISHED |
| Object | oppressor |
—
|
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: oppressor | Statement: [Joe Turner, ethicallyCharacterizedAs, oppressor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethicallyCharacterizedAs Context triple: [Joe Turner, ethicallyCharacterizedAs, oppressor]
-
A.
hasEthicalDimension
Indicates that the relationship, action, or situation involves moral considerations, value judgments, or ethical implications.
-
B.
hasEthicalRole
chosen
Indicates that an entity holds a position, function, or responsibility defined in terms of ethical duties, norms, or moral obligations in relation to another entity or context.
-
C.
hasEthicalIdeal
Indicates that an entity upholds or is guided by a particular ethical standard, principle, or ideal.
-
D.
hasEthicalStandard
Indicates that an entity adheres to, follows, or is governed by a specified set of ethical principles or standards.
-
E.
ethicsAssessment
Indicates that an entity has been evaluated or judged according to ethical principles, standards, or guidelines.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6618344c08190a3c918a41a871381 |
completed | May 2, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:10 a.m.