Triple
T1446915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States in tax litigation |
E31197
|
entity |
| Predicate | canBeSuedFor |
P28696
|
FINISHED |
| Object | tax refunds |
—
|
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: tax refunds | Statement: [United States in tax litigation, canBeSuedFor, tax refunds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSuedFor Context triple: [United States in tax litigation, canBeSuedFor, tax refunds]
-
A.
canBeAppealedTo
Indicates that a decision, action, or authority is subject to being challenged or reviewed by a higher or alternative authority through an appeal process.
-
B.
canBeChallengedOn
Indicates that one entity’s claim, decision, or status is open to being questioned, disputed, or formally contested by another entity.
-
C.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
D.
hasLegalIssue
Indicates that an entity is involved in, associated with, or subject to a legal problem, dispute, or proceeding.
-
E.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
- F. None of above. chosen
Provenance (4 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_69a499171a28819085b993a3ac78e363 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c558e0e081909802753872374d7b |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c47a840c819083307a65c027a19e |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.