Triple
T2783283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Three-Fifths Compromise |
E61746
|
entity |
| Predicate | endedEffectivelyBy |
P34990
|
FINISHED |
| Object | abolition of slavery in the United States |
—
|
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: abolition of slavery in the United States | Statement: [Three-Fifths Compromise, endedEffectivelyBy, abolition of slavery in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endedEffectivelyBy Context triple: [Three-Fifths Compromise, endedEffectivelyBy, abolition of slavery in the United States]
-
A.
endedFunctionallyWith
chosen
Indicates that a process, event, or relationship has effectively concluded in practice, even if it has not been formally or officially terminated.
-
B.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
C.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
D.
concludedBy
Indicates that an event, process, or state is brought to an end or finalized by a specific agent or entity.
-
E.
managedUntil
Indicates that one entity was responsible for managing or overseeing another entity up to a specific point in time.
- 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_69ab4b7e43c48190997b8fc8fb1663ab |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdd00b65c8190a8ea444308c4fa2b |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.