Triple
T2884886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voting Rights Act Amendments of 1975 |
E59481
|
entity |
| Predicate | addsProtectionFor |
P42575
|
FINISHED |
| Object | language minorities |
—
|
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: language minorities | Statement: [Voting Rights Act Amendments of 1975, addsProtectionFor, language minorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsProtectionFor Context triple: [Voting Rights Act Amendments of 1975, addsProtectionFor, language minorities]
-
A.
providesProtectionAgainst
Indicates that one entity serves to guard, shield, or defend another entity from a specified harm, threat, or adverse effect.
-
B.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
-
C.
addsProtectiveEmblem
Indicates that one entity applies or attaches a protective emblem or symbol to another entity.
-
D.
protectedFor
Indicates that something is safeguarded or preserved specifically for the benefit, use, or rights of a particular entity or purpose.
-
E.
isProtectedFor
Indicates that one entity is safeguarded or preserved specifically for the benefit, use, or rights of another entity.
- 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_69ab4ac739188190a112f42a5a69c951 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abe04476588190b0db0880e14c79b5 |
completed | March 7, 2026, 8:22 a.m. |
| PD | Predicate disambiguation | batch_69abdd15cbf08190bf7fea5ea516848a |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abdd96670c8190b727f9ac27dadf67 |
completed | March 7, 2026, 8:11 a.m. |
Created at: March 6, 2026, 10:03 p.m.