Triple
T7115910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Equal Rights Amendment |
E165818
|
entity |
| Predicate | extendedRatificationDeadline |
P50361
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Equal Rights Amendment, extendedRatificationDeadline, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendedRatificationDeadline Context triple: [Equal Rights Amendment, extendedRatificationDeadline, 1982]
-
A.
timeLimitForRatification
chosen
Indicates the deadline or maximum period allowed for an agreement, decision, or act to be formally ratified.
-
B.
timeFromProposalToRatification
Indicates the duration of time that passes between when a proposal is made and when it is formally ratified.
-
C.
extensionEffectiveDate
Indicates the date on which an extension to an existing agreement, term, or condition becomes effective.
-
D.
reasonForEventualRatification
Indicates the underlying cause or justification that led to the eventual ratification of something (such as a treaty, agreement, or decision).
-
E.
ratifiedAt
Indicates the date, time, or event context at which an agreement, treaty, or formal decision was officially ratified.
- 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_69c6888227bc8190a1394679e3116f90 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5f401b881909ef4c2ab1e0750db |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.