Triple
T17480020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone v. Graham |
E425630
|
entity |
| Predicate | foundPurposeOfLaw |
P99552
|
FINISHED |
| Object | plainly religious in nature |
—
|
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: plainly religious in nature | Statement: [Stone v. Graham, foundPurposeOfLaw, plainly religious in nature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundPurposeOfLaw Context triple: [Stone v. Graham, foundPurposeOfLaw, plainly religious in nature]
-
A.
foundationInLaw
Indicates that something is based on, justified by, or derives its authority from a specific law or legal framework.
-
B.
subjectOfLaw
Indicates that a law, legal document, or legal provision is about, concerns, or applies to the referenced subject.
-
C.
legalCodeFocus
Indicates that something is specifically concerned with, centered on, or primarily addressing a particular legal code or body of law.
-
D.
legalCodePurpose
chosen
Indicates that a legal code or statute exists for the purpose of achieving, regulating, or addressing a particular goal, issue, or function.
-
E.
appliedLawFrom
Indicates that a specific law or legal provision was applied or derived from a particular source, context, or jurisdiction in a legal decision or situation.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bf1e8081909f4d4b8992412e62 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.