Triple
T2412287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCI |
E52221
|
entity |
| Predicate | partyToDisputes |
P26178
|
FINISHED |
| Object | taxpayers |
—
|
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: taxpayers | Statement: [CCI, partyToDisputes, taxpayers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partyToDisputes Context triple: [CCI, partyToDisputes, taxpayers]
-
A.
partyToCase
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
B.
disputeInvolves
chosen
Indicates that a particular dispute includes or concerns the specified entities as participants or parties to the conflict.
-
C.
opposingParticipants
Indicates that the related entities are participants positioned in opposition to each other within the same interaction, event, or context.
-
D.
disputeOrigin
Indicates that there is disagreement or uncertainty about the source, cause, or initial point of something.
-
E.
negotiatingParty
Indicates that an entity is actively involved as a participant in a negotiation process with another entity.
- 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_69ab495622948190bc6bc6e4cddaf645 |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abc92a4e1c8190819fa676295ac145 |
completed | March 7, 2026, 6:43 a.m. |
| PD | Predicate disambiguation | batch_69abc5a6cbd0819086c0716e266b7ebb |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 6, 2026, 9:41 p.m.