Triple
T4717662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe G. Garcia |
E104686
|
entity |
| Predicate | caseCitationAssociated |
P17092
|
FINISHED |
| Object | 469 U.S. 528 |
—
|
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: 469 U.S. 528 | Statement: [Joe G. Garcia, caseCitationAssociated, 469 U.S. 528]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseCitationAssociated Context triple: [Joe G. Garcia, caseCitationAssociated, 469 U.S. 528]
-
A.
associatedCourtCase
chosen
Indicates a relationship where one entity is linked to, or involved in, a particular court case.
-
B.
legalCitationSystem
Indicates a system or convention used to reference and identify legal authorities such as cases, statutes, or regulations.
-
C.
relatedCase
Indicates that one legal case is connected or associated with another case, such as through shared facts, parties, issues, or procedural history.
-
D.
legalCaseOutcomeAssociatedWith
Indicates that a particular legal case outcome is connected or linked to a specific related entity, such as a case, party, or legal proceeding.
-
E.
legalCitation
Indicates that one legal document, case, or authority formally references or cites another as a source of legal support or precedent.
- 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_69bd43ec4a348190bc41afae43375e71 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:18 p.m.