Triple
T9607424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Utah v. Strieff |
E232006
|
entity |
| Predicate | concurringVote |
P4516
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Utah v. Strieff, concurringVote, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurringVote Context triple: [Utah v. Strieff, concurringVote, 1]
-
A.
concurringJustice
Indicates that a justice agrees with the court’s judgment or outcome but writes or joins a separate concurring opinion expressing different or additional reasoning.
-
B.
dissentingVoteBy
Indicates that a particular vote was cast in opposition to the majority or prevailing decision by a specific entity.
-
C.
hasConcurringJustice
chosen
Indicates that a judicial decision is associated with a justice who wrote or joined a concurring opinion.
-
D.
ratificationVote
Indicates a formal vote taken to approve, confirm, or give official sanction to a decision, agreement, or action.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69ca8485a90c819094fe40b42fde9d70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a62372881908bf21be91e7285fb |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.