Triple
T19037821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naim v. Naim |
E465921
|
entity |
| Predicate | courtReasoning |
P59235
|
FINISHED |
| Object | state’s interest in preserving racial integrity justified the ban |
—
|
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: state’s interest in preserving racial integrity justified the ban | Statement: [Naim v. Naim, courtReasoning, state’s interest in preserving racial integrity justified the ban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: courtReasoning Context triple: [Naim v. Naim, courtReasoning, state’s interest in preserving racial integrity justified the ban]
-
A.
courtReview
Indicates that a court formally examines a decision, action, or case to determine its legality, correctness, or appropriateness.
-
B.
reasonForJudgment
chosen
Indicates that a particular reason, basis, or justification underlies or explains a given judgment or decision.
-
C.
courtContext
Indicates the legal or judicial setting, circumstances, or framework within which a court-related action or relationship takes place.
-
D.
decisionCourt
Indicates that a particular court rendered the decision or judgment in a given legal case or proceeding.
-
E.
courtReported
Indicates that a court’s decision, proceedings, or judgment have been formally documented and made publicly available in a report or record.
- 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_69d8dd0359648190bc2a9202c5cf29d2 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d7fed99c81909495797c604db044 |
completed | April 20, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69e4a3001e388190aa6057266514e75a |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:02 p.m.