Triple
T27977831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jeannette Rankin |
E706537
|
entity |
| Predicate | votingPosition |
P35308
|
FINISHED |
| Object | opposed U.S. entry into World War I |
—
|
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: opposed U.S. entry into World War I | Statement: [Jeannette Rankin, votingPosition, opposed U.S. entry into World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingPosition Context triple: [Jeannette Rankin, votingPosition, opposed U.S. entry into World War I]
-
A.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
-
B.
positionInReferendum
Indicates the stance or role an entity holds regarding a specific referendum.
-
C.
positionOnVotingRights
Indicates a stance or viewpoint that an entity holds regarding policies or issues related to voting rights.
-
D.
positionOnBallot
Indicates the specific ordered place that a candidate or option occupies on an election ballot.
-
E.
voteRecord
chosen
Indicates that an entity has cast a specific vote or holds a particular voting position in a given decision or election.
- 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 7:42 p.m.