Triple
T28361968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynch v. Donnelly |
E718384
|
entity |
| Predicate | hasPlaintiffOrPetitioner |
P152662
|
FINISHED |
| Object | Dennis Lynch |
—
|
NE NERFINISHED |
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: Dennis Lynch | Statement: [Lynch v. Donnelly, hasPlaintiffOrPetitioner, Dennis Lynch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaintiffOrPetitioner Context triple: [Lynch v. Donnelly, hasPlaintiffOrPetitioner, Dennis Lynch]
-
A.
casePetitioner
chosen
Indicates that an entity is the party who formally brings or initiates a legal case or petition before a court or tribunal.
-
B.
partyTypePlaintiffs
Indicates the classification or category of the parties serving as plaintiffs in a legal action.
-
C.
hasDefendants
Indicates that one or more entities serve as defendants in relation to a particular legal case or proceeding.
-
D.
hasMainDefendant
Indicates that a legal case or proceeding identifies a specific individual or entity as its primary defendant.
-
E.
leadPlaintiffIn
Indicates that one entity serves as the primary or representative plaintiff in a legal case involving 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 12:52 a.m.