Triple
T12889193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Section 10 of the Voting Rights Act of 1965 |
E308312
|
entity |
| Predicate | decisionYearOfKeyChallenge |
P2233
|
FINISHED |
| Object | 1966 |
—
|
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: 1966 | Statement: [Section 10 of the Voting Rights Act of 1965, decisionYearOfKeyChallenge, 1966]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionYearOfKeyChallenge Context triple: [Section 10 of the Voting Rights Act of 1965, decisionYearOfKeyChallenge, 1966]
-
A.
decisionPublication
Indicates that a decision has been formally published or made publicly available.
-
B.
yearDecided
chosen
Indicates the specific calendar year in which a decision, ruling, or resolution was formally made or finalized.
-
C.
decisionImplementedBy
Indicates that a particular decision is carried out, executed, or put into effect by a specified agent or entity.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decisionHolding
Indicates that an entity has made, issued, or is responsible for a particular formal decision or ruling.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714581988190afc720ffd7797860 |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:39 p.m.