Triple
T181578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lost Cause ideology |
E3887
|
entity |
| Predicate | denigrates |
P3077
|
FINISHED |
| Object | Reconstruction policies |
—
|
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: Reconstruction policies | Statement: [Lost Cause ideology, denigrates, Reconstruction policies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: denigrates Context triple: [Lost Cause ideology, denigrates, Reconstruction policies]
-
A.
derogatesFrom
chosen
Indicates that one entity diminishes, belittles, or detracts from the value, reputation, or importance of another entity.
-
B.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
C.
condemnation
Indicates that an entity expresses strong disapproval or denunciation of another entity, action, or situation.
-
D.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
-
E.
negativeFormulation
Indicates that the associated statement, condition, or requirement is expressed in a negated or prohibitive form rather than an affirmative one.
- 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a25923507c8190bd7f6eda404b0da0 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566ccc288190add5624ede96d82b |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.