Triple
T2618547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 4(b) of the Voting Rights Act of 1965 |
E58948
|
entity |
| Predicate | limitedByDecisionOn |
P8832
|
FINISHED |
| Object | June 25, 2013 |
—
|
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: June 25, 2013 | Statement: [Section 4(b) of the Voting Rights Act of 1965, limitedByDecisionOn, June 25, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: limitedByDecisionOn Context triple: [Section 4(b) of the Voting Rights Act of 1965, limitedByDecisionOn, June 25, 2013]
-
A.
decisionsSubjectTo
Indicates that certain decisions are constrained by, dependent on, or must comply with specified conditions, approvals, or oversight.
-
B.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
C.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
D.
limitedByCourtCase
chosen
Indicates that one entity’s scope, effect, or applicability is restricted or constrained as a result of a specific court case or legal proceeding.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.