Triple
T16961979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana small claims courts |
E411451
|
entity |
| Predicate | filingParty |
P15954
|
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: [Indiana small claims courts, filingParty, plaintiff]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filingParty Context triple: [Indiana small claims courts, filingParty, plaintiff]
-
A.
participatingParty
Indicates that an entity is involved as a participant in a particular event, activity, or transaction.
-
B.
partyToCase
chosen
Indicates that an entity is involved in a legal case as one of its formal participants (e.g., plaintiff, defendant, or other party).
-
C.
decliningParty
Indicates that an entity refuses, rejects, or turns down an offer, request, or proposal made by another entity.
-
D.
filedWith
Indicates that one entity has officially submitted or registered something (such as a document, complaint, or application) to another entity or authority.
-
E.
legalParties
Indicates that the related entities are formally recognized participants in a legal relationship, case, contract, or proceeding.
- 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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d021c5508190b6e3106554c07a9c |
completed | April 18, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69e32b9cddf88190bc42709604047353 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:31 a.m.