Triple
T22061402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herring v. United States |
E545159
|
entity |
| Predicate | votingSplit |
P4510
|
FINISHED |
| Object | 5-4 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: 5-4 decision | Statement: [Herring v. United States, votingSplit, 5-4 decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSplit Context triple: [Herring v. United States, votingSplit, 5-4 decision]
-
A.
voteSplit
Indicates that a voting outcome is divided among multiple options or parties rather than being unanimous or clearly majority.
-
B.
hasVoteSplit
chosen
Indicates that a collective decision or vote resulted in differing choices among participants rather than unanimous agreement.
-
C.
oppositionSplit
Indicates that a previously unified opposing group or force has divided into separate, conflicting parts.
-
D.
votePattern
Indicates a recurring way or tendency in how an entity casts votes across issues, candidates, or time.
-
E.
voteResult
Indicates the outcome or decision produced by a voting process involving the related entities.
- 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_69e11e3377c48190890c17407b9527d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1285d5e508190b3124a70fe55b32e |
completed | April 28, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69e6f643ca74819083e8ab78e843f243 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.