Triple
T25603128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equal Rights Amendment |
E641838
|
entity |
| Predicate | stateRatificationsBy1982 |
P74640
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Equal Rights Amendment, stateRatificationsBy1982, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRatificationsBy1982 Context triple: [Equal Rights Amendment, stateRatificationsBy1982, 35]
-
A.
numberOfStatesRatifiedBy1982
chosen
Indicates the number of states that had ratified a given item (such as a treaty, amendment, or agreement) by the year 1982.
-
B.
stateOfFirstRatification
Indicates the state in which an agreement, treaty, or document was first formally ratified.
-
C.
charterRatificationStatusInUS
Indicates the status of whether a given charter has been ratified within the United States.
-
D.
numberOfStatesRequiredForRatification
Indicates the specific number of states that must approve or ratify a proposal for it to become valid or effective.
-
E.
ratifiedBy
Indicates that an agreement, treaty, or decision has been formally approved and made officially valid by a specified authority or body.
- 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_69e75dc6ccf081908d49578fd36a76d5 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 21, 2026, 4:36 p.m.