Triple
T3885199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 26 U.S.C. § 6672 |
E92922
|
entity |
| Predicate | liabilityNature |
P4329
|
FINISHED |
| Object | joint and several liability among responsible persons |
—
|
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: joint and several liability among responsible persons | Statement: [26 U.S.C. § 6672, liabilityNature, joint and several liability among responsible persons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liabilityNature Context triple: [26 U.S.C. § 6672, liabilityNature, joint and several liability among responsible persons]
-
A.
establishesLiabilityFor
chosen
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
B.
legalRulingNature
Indicates the type or character of a legal ruling, such as its form, basis, or procedural nature.
-
C.
authorityNature
Indicates the type or character of authority one entity holds or exercises over another.
-
D.
legalSubject
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
E.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec92cc548190b88b899299e5ccdc |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.