Triple
T20760074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States v. Susan B. Anthony |
E510953
|
entity |
| Predicate | laterContext |
P16227
|
FINISHED |
| Object | preceded the eventual adoption of the Nineteenth Amendment |
—
|
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: preceded the eventual adoption of the Nineteenth Amendment | Statement: [United States v. Susan B. Anthony, laterContext, preceded the eventual adoption of the Nineteenth Amendment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterContext Context triple: [United States v. Susan B. Anthony, laterContext, preceded the eventual adoption of the Nineteenth Amendment]
-
A.
laterScope
Indicates that one event, state, or condition occurs or applies after the temporal scope of another.
-
B.
laterController
Indicates that one entity assumes control, authority, or responsibility after another entity, succeeding it in time.
-
C.
laterBase
Indicates that one event, state, or version occurs or is valid at a later time than another referenced event, state, or version.
-
D.
successorContext
chosen
Indicates that one context directly follows and continues from another in a sequence or process.
-
E.
laterExtendedIn
Indicates that an existing entity (such as a work, version, or specification) was subsequently expanded, updated, or built upon by a later entity.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24751688190829f9d836abfb606 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.