Triple
T26228352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha Elauf |
E655958
|
entity |
| Predicate | legalCaseVote |
P178261
|
FINISHED |
| Object | 8–1 decision |
—
|
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: 8–1 decision | Statement: [Samantha Elauf, legalCaseVote, 8–1 decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCaseVote Context triple: [Samantha Elauf, legalCaseVote, 8–1 decision]
-
A.
voteOn
Indicates that an entity formally expresses a choice or decision regarding a specific proposal, issue, or candidate.
-
B.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
-
C.
voteProcess
Indicates the formal procedure by which participants cast and record their votes to reach a decision or outcome.
-
D.
voteType
Indicates the specific category or kind of vote associated with an action or decision (e.g., upvote, downvote, approval, rejection).
-
E.
voteRecord
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. chosen
Provenance (4 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 26, 2026, 8:58 p.m.