Triple
T125992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wickard v. Filburn |
E2551
|
entity |
| Predicate | hasDecisionType |
P2165
|
FINISHED |
| Object | unanimous decision |
—
|
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: unanimous decision | Statement: [Wickard v. Filburn, hasDecisionType, unanimous decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDecisionType Context triple: [Wickard v. Filburn, hasDecisionType, unanimous decision]
-
A.
decisionType
chosen
Indicates the specific category or nature of a decision associated with an entity or event.
-
B.
decidesOn
Indicates that an agent makes a choice or determination regarding a particular option, issue, or course of action.
-
C.
associatedWithDecision
Indicates a relationship where an entity is linked or connected to a particular decision, such that the decision is relevant to, influenced by, or otherwise tied to that entity.
-
D.
decides
Indicates that an entity makes a choice or determination between options, often resolving uncertainty or selecting a course of action.
-
E.
decisionLanguage
Indicates that a decision, statement, or choice is expressed or recorded in a particular natural language.
- 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_69a251b54ea88190b18281669f59b4c0 |
completed | Feb. 28, 2026, 2:23 a.m. |
| NER | Named-entity recognition | batch_69a25760af348190bf402089c240887d |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a2564c11208190ad25495609d94d87 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:27 a.m.