Triple
T48594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvering v. Davis |
E954
|
entity |
| Predicate | areaOfLaw |
P2167
|
FINISHED |
| Object | constitutional law |
—
|
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: constitutional law | Statement: [Helvering v. Davis, areaOfLaw, constitutional law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areaOfLaw Context triple: [Helvering v. Davis, areaOfLaw, constitutional law]
-
A.
legalArea
chosen
Indicates the specific field or branch of law that a legal matter, case, or document pertains to.
-
B.
legalSystem
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
C.
constitutionalDomain
Indicates that something falls within the scope, authority, or subject matter defined or governed by a particular constitution.
-
D.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
E.
legalContext
Indicates that the relationship or action occurs within, is shaped by, or is relevant to a specific legal framework, proceeding, or set of legal norms.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.