Triple
T6169152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Student Succeeds Act |
E137646
|
entity |
| Predicate | shiftsAuthorityTo |
P39302
|
FINISHED |
| Object | states |
—
|
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: states | Statement: [Every Student Succeeds Act, shiftsAuthorityTo, states]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shiftsAuthorityTo Context triple: [Every Student Succeeds Act, shiftsAuthorityTo, states]
-
A.
shiftedAuthorityTo
chosen
Indicates that decision-making power or control has been transferred from one entity to another.
-
B.
reaffirmsAuthorityOf
Indicates that one entity confirms, strengthens, or restates the legitimacy or power of another entity’s authority.
-
C.
shiftedTariffAuthorityTo
Indicates that decision-making power over tariffs was transferred from one entity to another.
-
D.
hasAssigningAuthority
Indicates that one entity serves as the official source or authority responsible for assigning or issuing identifiers, codes, or designations to another entity.
-
E.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d8de56481909583104c70a52616 |
completed | March 22, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_69c055f7f12881908e21c04e9b752ba4 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:18 p.m.