Triple
T19570193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark of Cain |
E489687
|
entity |
| Predicate | misusedIn |
P4002
|
FINISHED |
| Object | racist ideologies (historically) |
—
|
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: racist ideologies (historically) | Statement: [Mark of Cain, misusedIn, racist ideologies (historically)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: misusedIn Context triple: [Mark of Cain, misusedIn, racist ideologies (historically)]
-
A.
misappliedAs
chosen
Indicates that something has been used, interpreted, or assigned in an incorrect, inappropriate, or unintended way.
-
B.
misinterpretedBy
Indicates that something (such as a statement, action, or signal) is understood incorrectly or in a way not intended by a particular entity.
-
C.
misuseCanConstitute
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
-
D.
misl
Indicates a relationship where one entity is incorrectly labeled, classified, or identified as another.
-
E.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402043588190a99f5a55c5dcd8a6 |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514d4df3c8190b7e9b3b4fdf9452a |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:42 p.m.