Triple
T12029232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Defense of Marriage Act |
E286357
|
entity |
| Predicate | sectionStruckDown |
P25040
|
FINISHED |
| Object | Section 3 |
—
|
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 3 | Statement: [Defense of Marriage Act, sectionStruckDown, Section 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sectionStruckDown Context triple: [Defense of Marriage Act, sectionStruckDown, Section 3]
-
A.
struckDownProvision
chosen
Indicates that a legal authority has invalidated or nullified a specific provision, rendering it without legal effect.
-
B.
canStrikeDown
Indicates that one entity has the authority or power to invalidate, nullify, or overturn another entity, action, or decision.
-
C.
enforcementMechanismStruckDown
Indicates that a legal or regulatory enforcement mechanism has been invalidated or nullified, typically by a court or authoritative body.
-
D.
repealedUnder
Indicates that one legal rule, law, or regulation has been formally revoked or annulled by virtue of another specified legal authority or provision.
-
E.
section
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
- 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.