Triple
T16599781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifteenth Amendment Enforcement Clause |
E403300
|
entity |
| Predicate | yearEffectiveWithAmendment |
P52537
|
FINISHED |
| Object | 1870 |
—
|
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: 1870 | Statement: [Fifteenth Amendment Enforcement Clause, yearEffectiveWithAmendment, 1870]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearEffectiveWithAmendment Context triple: [Fifteenth Amendment Enforcement Clause, yearEffectiveWithAmendment, 1870]
-
A.
effectiveYear
Indicates the calendar year in which something (such as a rule, status, or agreement) becomes valid or takes effect.
-
B.
lessEffectiveAt
Indicates that one entity has a reduced ability or lower level of success in performing, influencing, or achieving a particular action or outcome compared to another.
-
C.
repealEffectiveIn
Indicates that a repeal of a law, rule, or regulation becomes legally operative within a specified jurisdiction or context.
-
D.
amendmentYear
chosen
Indicates the year in which an amendment to a law, document, or agreement was formally made or enacted.
-
E.
constitutionEffectiveFrom
Indicates the date or point in time from which a particular constitution or constitutional provision is legally in force and applicable.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d75772c8190b02aef02ea6788e1 |
completed | April 18, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_69e296aabc508190b3836a91b49113ad |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.