Triple
T1446909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States in tax litigation |
E31197
|
entity |
| Predicate | roleInCollectionSuit |
P27764
|
FINISHED |
| Object | plaintiff |
—
|
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: plaintiff | Statement: [United States in tax litigation, roleInCollectionSuit, plaintiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCollectionSuit Context triple: [United States in tax litigation, roleInCollectionSuit, plaintiff]
-
A.
servesRole
Indicates that one entity performs, fulfills, or occupies a particular function, position, or responsibility in relation to another entity.
-
B.
partOfCollection
Indicates that an entity belongs to, or is included within, a larger collection or set.
-
C.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
hasNotableRoleIn
chosen
Indicates that an entity holds a significant or noteworthy role or function within another entity, event, work, or context.
-
E.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
- 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_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. |
Created at: March 1, 2026, 8 p.m.