Triple
T2000705
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cutter v. Wilkinson |
E43462
|
entity |
| Predicate | concernsTopic |
P11116
|
FINISHED |
| Object | free exercise of religion |
—
|
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: free exercise of religion | Statement: [Cutter v. Wilkinson, concernsTopic, free exercise of religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concernsTopic Context triple: [Cutter v. Wilkinson, concernsTopic, free exercise of religion]
-
A.
concern
chosen
Indicates that one entity is about, relates to, or is of interest or importance to another entity.
-
B.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
-
C.
raisedConcernAbout
Indicates that one entity has expressed worry, doubt, or objection regarding another entity or issue.
-
D.
concernsLayer
Indicates that something is related or pertains specifically to a particular layer within a layered structure or system.
-
E.
socialConcern
Indicates a relationship where an entity is concerned about, attentive to, or actively engaged with social issues, problems, or well-being.
- 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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb87f78f0819098e787a5f3e062fd |
completed | March 7, 2026, 5:32 a.m. |
| PD | Predicate disambiguation | batch_69abb79e63c08190982c8b44a557266f |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:37 p.m.