Triple
T3981304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 42 U.S.C. § 1983 |
E85763
|
entity |
| Predicate | enactedAs |
P53171
|
FINISHED |
| Object | Section 1 of the Civil Rights Act of 1871 |
—
|
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: Section 1 of the Civil Rights Act of 1871 | Statement: [42 U.S.C. § 1983, enactedAs, Section 1 of the Civil Rights Act of 1871]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enactedAs Context triple: [42 U.S.C. § 1983, enactedAs, Section 1 of the Civil Rights Act of 1871]
-
A.
enactedBy
Indicates that a law, policy, or formal measure is officially established or brought into effect by a specific authority or governing body.
-
B.
enactedAfter
Indicates that one enactment event occurred later in time than another enactment event.
-
C.
enactedDuring
Indicates that an action, event, or state occurred within the temporal span of a specified time period or event.
-
D.
enactedInResponseTo
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
-
E.
signedIntoLawIn
Indicates that a proposed law or bill was formally approved and enacted by an authorized official in a specific place or jurisdiction.
- F. None of above. chosen
Provenance (4 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa3cf4048190837f9ec5fa8e95e3 |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:33 p.m.