Triple
T537181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherbert v. Verner |
E12350
|
entity |
| Predicate | burdenFound |
P16588
|
FINISHED |
| Object | substantial burden on religious practice |
—
|
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: substantial burden on religious practice | Statement: [Sherbert v. Verner, burdenFound, substantial burden on religious practice]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burdenFound Context triple: [Sherbert v. Verner, burdenFound, substantial burden on religious practice]
-
A.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
-
B.
encountered
Indicates that one entity came across or met another entity, typically in a specific place or context, often unexpectedly or during the course of some activity.
-
C.
hasFindingAid
Indicates that there exists a documented guide or tool that helps users locate, understand, and access the materials within a collection or resource.
-
D.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
E.
carriedBy
Indicates that one entity is physically supported and transported by another entity.
- F. None of above. chosen
Provenance (4 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_69a4933208e88190891f5debab1b776d |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4985e51908190a34aa82ea9dbee1e |
completed | March 1, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69a494b51ff08190a39f4168fd9a7ddf |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a49857e1148190aa782b82675cf0b5 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.