Triple
T9894953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia Minor women’s suffrage case |
E181546
|
entity |
| Predicate | involvesRight |
P90035
|
FINISHED |
| Object | right to vote |
—
|
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: right to vote | Statement: [Virginia Minor women’s suffrage case, involvesRight, right to vote]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesRight Context triple: [Virginia Minor women’s suffrage case, involvesRight, right to vote]
-
A.
rightInvolved
chosen
Indicates that an entity is involved in or associated with a legal or formal right held, exercised, or affected in a given context.
-
B.
involves
Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
-
C.
incorporatesRight
Indicates that one entity includes, absorbs, or integrates another entity as a component or part within itself.
-
D.
oftenInvolvedWith
Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
-
E.
involvedAction
Indicates that an entity participates in, performs, or is otherwise engaged in a specified action or activity.
- 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_69ca8283a6708190801af7a25a7ebb9f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a89e148190901753e67483d72c |
completed | April 2, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69cd1d872d50819096b7ab166a8decf1 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:39 p.m.