Triple
T808822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reed v. Reed |
E17496
|
entity |
| Predicate | appliedStandardOfReview |
P3850
|
FINISHED |
| Object | rational basis review |
—
|
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: rational basis review | Statement: [Reed v. Reed, appliedStandardOfReview, rational basis review]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedStandardOfReview Context triple: [Reed v. Reed, appliedStandardOfReview, rational basis review]
-
A.
standardOfReview
chosen
Indicates the level and type of scrutiny an authority (such as a court or reviewer) applies when evaluating a prior decision, action, or finding.
-
B.
standardApplied
Indicates that a particular standard, rule, or guideline has been put into effect or used as the basis for an action or decision in the relationship.
-
C.
standardOfProof
Indicates the level or degree of certainty required to establish that a claim or allegation is true in a given context.
-
D.
appliedInJurisdiction
Indicates that a rule, decision, or action is put into effect or holds legal force within a specified jurisdiction.
-
E.
appliedTest
Indicates that a test has been administered or carried out on a particular subject or object.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.