Triple
T24926765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paula Rosalee Corbin |
E618878
|
entity |
| Predicate | lawsuitSettlementAdmissionOfLiability |
P157174
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Paula Rosalee Corbin, lawsuitSettlementAdmissionOfLiability, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lawsuitSettlementAdmissionOfLiability Context triple: [Paula Rosalee Corbin, lawsuitSettlementAdmissionOfLiability, no]
-
A.
settlementAdmissionOfLiability
chosen
Indicates that a party’s settlement includes an explicit acknowledgment or acceptance of legal responsibility for the underlying claim or harm.
-
B.
legalConclusion
Indicates that a situation, set of facts, or argument leads to or supports a specific determination or outcome under the law.
-
C.
lawsuitSettlementYear
Indicates the year in which a lawsuit between parties was formally settled or resolved.
-
D.
settledAs
Indicates that one entity has been resolved, finalized, or agreed upon in the form or status of another entity.
-
E.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
- 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 18, 2026, 5:29 a.m.