Triple
T48614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Helvering v. Davis |
E954
|
entity |
| Predicate | typeOfDecision |
P2165
|
FINISHED |
| Object | upholding federal statute |
—
|
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: upholding federal statute | Statement: [Helvering v. Davis, typeOfDecision, upholding federal statute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDecision Context triple: [Helvering v. Davis, typeOfDecision, upholding federal statute]
-
A.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
C.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
D.
decisionLanguage
Indicates that a decision, statement, or choice is expressed or recorded in a particular natural language.
-
E.
unanimousDecision
Indicates that all relevant participants fully agree on a decision without any dissent.
- 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.