Triple
T38037888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State Hecht–Calandra Act |
E949399
|
entity |
| Predicate | reformProposals |
P189897
|
FINISHED |
| Object | repeal of test-only mandate |
—
|
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: repeal of test-only mandate | Statement: [New York State Hecht–Calandra Act, reformProposals, repeal of test-only mandate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformProposals Context triple: [New York State Hecht–Calandra Act, reformProposals, repeal of test-only mandate]
-
A.
notableProposal
Indicates that an entity is a proposal distinguished by particular significance, impact, or recognition compared to other proposals.
-
B.
proposedAmendment
Indicates that one entity has formally suggested a change or addition (an amendment) to another entity, such as a document, law, or agreement.
-
C.
proposedLaw
Indicates that an entity has formally put forward a law or legislative measure for consideration or approval.
-
D.
relatedProposal
Indicates that one proposal has a specified relationship or association with another proposal.
-
E.
proposalType
Indicates the specific category or kind of proposal associated with an entity or event.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fc44c67118819088accfeded7b449e |
completed | May 7, 2026, 7:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.