Triple
T424738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compromise of 1850 |
E8181
|
entity |
| Predicate | abolishes |
P9435
|
FINISHED |
| Object | slave trade in Washington, D.C. |
—
|
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: slave trade in Washington, D.C. | Statement: [Compromise of 1850, abolishes, slave trade in Washington, D.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishes Context triple: [Compromise of 1850, abolishes, slave trade in Washington, D.C.]
-
A.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
B.
abolishedConcept
chosen
Indicates that one entity has formally ended, eliminated, or done away with the other entity as a concept, practice, or institution.
-
C.
doesNotAbolish
Indicates that one entity, action, or law does not eliminate, revoke, or put an end to another.
-
D.
reduces
Indicates that one entity causes a decrease in the amount, intensity, degree, or impact of another entity.
-
E.
affirms
Indicates that one entity explicitly confirms, supports, or asserts the truth or validity of another entity, statement, or proposition.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed56ab481909eec289075496260 |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd6736c81909a6ca549f77b4345 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.