Triple
T32152770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swain v. Alabama |
E821201
|
entity |
| Predicate | isRelatedDoctrine |
P41967
|
FINISHED |
| Object | Batson challenge |
—
|
NE NERFINISHED |
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: Batson challenge | Statement: [Swain v. Alabama, isRelatedDoctrine, Batson challenge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRelatedDoctrine Context triple: [Swain v. Alabama, isRelatedDoctrine, Batson challenge]
-
A.
isRelevantToDoctrine
chosen
Indicates that something has a meaningful connection or applicability to a particular doctrine, principle, or set of beliefs.
-
B.
sharesDoctrine
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
C.
citedForDoctrine
Indicates that one entity is cited as an authoritative source or precedent for a particular doctrine, principle, or rule in relation to another entity.
-
D.
concernsDoctrine
Indicates that something is related or pertains specifically to a particular doctrine or set of doctrinal principles.
-
E.
containsDoctrine
Indicates that one entity includes, embodies, or incorporates the doctrine, principles, or teachings represented by another entity.
- 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9eccab88190a2895cbb0332c5a7 |
completed | May 3, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:32 a.m.