Triple
T12654941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregory |
E302255
|
entity |
| Predicate | litigantType |
P16985
|
FINISHED |
| Object | petitioner |
—
|
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: petitioner | Statement: [Gregory, litigantType, petitioner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: litigantType Context triple: [Gregory, litigantType, petitioner]
-
A.
litigationType
Indicates the specific category or nature of a legal dispute or court case associated with an entity or event.
-
B.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
litigates
Indicates that one party engages in legal action or conducts a lawsuit against or involving another party.
-
D.
litigatesBefore
Indicates that a legal case or dispute is argued or conducted in front of a particular court or judicial body.
-
E.
legalCaseRole
chosen
Indicates the specific role or capacity an entity holds within a legal case, such as plaintiff, defendant, judge, or attorney.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:18 p.m.